When a Windows build has insufficient symbols, the XPCOM stack walker should print library+offset rather than badsym+offset. Preferably in the same format that Mac and Linux use. I'd accept both (e.g. library+offset + badsym+offset) if it's hard to detect whether the symbols available to the stack walker are "insufficient". This would allow Windows Tinderbox tests to use fix_stack_using_bpsyms.py and get decent stack traces.
Created attachment 454451 [details] example of good output from a local debug build The Windows stack walker actually works really well on non-stripped builds. It's only stripped builds that would benefit from this change.
Fixing this might be as simple as grabbing aDetails->loffset in NS_FormatCodeAddressDetails. But I get disoriented by all the ifdefs in nsStackWalk.cpp.
Fixing this would help debug assertions that are only seen on tinderbox. I've got a few right now that I can't reproduce locally, and are windows only :(
In fact, I'd say that it's preventing me from fixing bug 599969 (blocker).
Blocking, since it blocks a blocker.
6 years ago
Fixed by Ted as part of his patch in bug 751673.
I kinda forgot there was a bug on this.