https://bugzilla.novell.com/show_bug.cgi?id=342603#c13
--- Comment #13 from Robert Kaiser 2007-11-22 16:05:46 MST ---
Created an attachment (id=184460)
--> (https://bugzilla.novell.com/attachment.cgi?id=184460)
backtrace and some debugging from debug build
I can confirm that recompiling only nsEventStateManager.cpp with -O0 instead of
-Os (but leaving all other options as-is) makes the crash go away.
The attached stacktrace and a bit of further output makes it clear that
http://mxr.mozilla.org/seamonkey/source/content/events/src/nsEventStateManag...
is the call where the bug is already present (mActiveContent being null, which
is handed down to the state where that pointer is dereferenced). When
everything is compiled as usual, this never ends up being null, but some
optimization in current gcc 4.3 causes that pointer to end up as null. We never
saw this with older compilers and don't see this when that file is not compiled
with optimiziation, so it looks a lot like a compiler error.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.