No stack trace when running alive tests on debug builds



9 years ago
5 years ago


(Reporter: catlee, Assigned: ted)


Firefox Tracking Flags

(Not tracked)




9 years ago
Initial report here:

We're not setting MINIDUMP_STACKWALK when running the alive tests on debug builds, so we don't get stack traces if we crash.
Nick's log there is the same as comment 0, presumably he meant to link to something else.
Assignee: nobody → ted.mielczarek
Unsure if this has the same root cause as bug 519194, we should look and see.
Nick, if you could find an actual occurrence of this problem, that'd help.
Try the output from "python -- -CreateProfile default" at the end of this

It may just be we handle the leak incorrectly, but it also seems very weird that we're hitting all those URLs when creating a profile. and friends, and the IDN stuff, look bogus.
The list of URLs is just from the proxy PAC stuff does:
using the list here:

since uses the initializeProfile call from there:

Back to the point, it looks like MINIDUMP_STACKWALK wasn't set there. When I fixed the other bug about stacks without symbols, I left in some debug prints, so if we hit this in the future it should be more readily obvious why there's no stack printed:
Of course, looking at, it looks like we'll have other problems, since it doesn't currently take any arguments at all, so you can't pass in --symbols-path.
This appears fixed in our buildbotcustom code now:

Fixing the accessory issue of not setting --symbols-path in bug 542952.
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.