Closed Bug 519194 Opened 15 years ago Closed 15 years ago

No symbols in stack trace on tests of optimized builds

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(status1.9.2 beta2-fixed, status1.9.1 .6-fixed)

RESOLVED FIXED
Tracking Status
status1.9.2 --- beta2-fixed
status1.9.1 --- .6-fixed

People

(Reporter: catlee, Assigned: ted)

References

Details

From initial report here: https://bugzilla.mozilla.org/show_bug.cgi?id=518634#c0

Unittests on an optimized Linux builds crashed.  We got a stack trace, but without symbols.
I suggested that we should grab one of these builds + associated symbols, unpack them somewhere, run the browser, kill it to get a minidump, and try running minidump_stackwalk with that dump + the symbols to sanity check that it works.
I tried this locally and the stack trace came out with symbols. I grabbed the build + symbols from this build:
http://tinderbox.mozilla.org/showlog.cgi?tree=Firefox-Unittest&errorparser=unittest&logfile=1254150797.1254152377.1343.gz&buildtime=1254150797&buildname=Linux%20mozilla-central%20test%20opt%20mochitests&fulltext=1

Which had a crash and displayed a stack trace without symbols. It looks like the symbols are unpacked in the right place, and the runtests.py commandline references them properly. I'm not sure what's going on here.
Assignee: catlee → ted.mielczarek
I'm not sure how this ever worked, honestly, but I pushed a fix:
http://hg.mozilla.org/mozilla-central/rev/0f0239688a76
(I also left in some extra debug output in there, to give more info in case MINIDUMP_STACKWALK isn't set.)

I was able to reproduce the problem locally using a build+packaged tests, and this patch fixed it.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Depends on: 523330
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.