Missing stacks when running mochitests
Categories
(Testing :: Mochitest, defect, P3)
Tracking
(Not tracked)
People
(Reporter: beth, Assigned: gbrown)
References
Details
Attachments
(1 file)
17.60 KB,
text/plain
|
Details |
I was running some tests on a local linux build and was crashing but not receiving any stack output. This was due to this check in utils.py.
However, the build I was testing was an "optdebug" build, ie, optimized with both debug symbols and debug assertions. From my mozconfig:
ac_add_options --enable-optimize
ac_add_options --enable-debug
ac_add_options --enable-debug-symbols
I would therefore expect stacks to be printed during a crash.
I was able to get stacks in my crash by:
- Removing the check in utils.py
- Building minidump_stackwalk by adding
ac_add_options --enable-project/tools/crashreporter
- Running
./mach buildsymbols
- Running the test with
MINIDUMP_STACKWALK
set to the executable from step 2.
It would be nice if this was officially supported by tooling because stacks seem possible in the situation.
Reporter | ||
Comment 1•5 years ago
|
||
Here is a log that results when I don't apply the workarounds outlined in the bug.
![]() |
Assignee | |
Comment 2•5 years ago
|
||
The first thing I notice in the log is:
MINIDUMP_STACKWALK not set, can't process dump.
The first step in crash reporting is to run any minidumps through minidump_stackwalk, found via the MINIDUMP_STACKWALK environment variable: You do need to set that locally to get crash reports.
There has also been activity around fix-stacks, with a current discussion in https://groups.google.com/forum/#!topic/mozilla.dev.platform/y_k0X4Y6t1g ... but none of that comes into play until minidump_stackwalk has generated a crash report.
![]() |
Assignee | |
Comment 3•5 years ago
|
||
Be aware that rather than building minidump_stackwalk locally, it may be easier to download one from CI, like
Comment 4•5 years ago
•
|
||
If I'm reading comment 2 correctly, it looks like there's no bug to fix? Do we want to resolve or is there still something to improve?
Updated•5 years ago
|
![]() |
Assignee | |
Comment 5•5 years ago
|
||
With bug 1635834 (or the tc index, comment 3), minidump_stackwalk is readily available, and developers need only set their environment's MINIDUMP_STACKWALK to point to their local copy, if they want crash reports.
Description
•