On 2010-12-27 10:39 PDT, Matej Kurpel wrote: > Wow - I was able to "Attach To Process..." in VS2008 and then I caused > the crash deliberately.
Bravo. > It showed me the source code and call stack, which is great. But > evaluating most of the variables returned "CXX0069: Error: variable > needs stack frame". No idea what that means. The code at which you were looking was compiled with "Frame Pointer Optimization" (FPO), which causes the compiler to NOT use one of the registers for its usual purpose, acting as a pointer to the function's local variables, and instead use it as a general purpose registers. The debugger you're using is confused by that. I don't know how you can work around it. Assuming that you ARE using the symbols from Mozilla's symbols server, perhaps you need to use a newer version of the Visual Studio debugger. Perhaps you need to tell your VS Debugger to expect FPO somehow (e.g. a settable option). You might ask about this debugging issue in mozilla.dev.builds. I think if anyone would know how to work around FPO, they would. In any case, the code you're examining is not NSS code nor PSM code. The people in this group are not the experts in that code. You need help from the Thunderbird developers. > I am sending you the call stack as VS displayed it to me. It crashed on > a line in nsGlobalWindow.cpp saying: > > nsWindowSH::InvalidateGlobalScopePolluter(cx, currentInner->mJSObject); > > saying Uncaught exception occurred. > > Call stack: The stack you supplied shows a NULL value for "aState" being passed several levels down the stack. That's suspicious, but not necessarily a bug. I'd suggest you find the caller that first passes that NULL value, and look at the code that does that. Perhaps you will find some clues about the problem there. > Anything more I could do? Yes, file a bug report in bugzilla.mozilla.org, product Thunderbird. Include all the stack info and other info you provided in the email to which I am responding. If you have Thunderbird crash IDs (look like GUIDs) that might have been previously reported by your TBird to Mozilla, include those. But don't expect a quick response. You may add my email address to the CC list on your new bug report. That won't hasten a solution, but it will satisfy my curiosity. :) Regards, -- /Nelson Bolyard -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
