mozilla-firefox 0.9.3-6 crash
I have been experiencing inexplicable, apparently random crashes of
I'm running unstable, fluxbox wm, nvidia driver.
I receive this on the crash:
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadShmSeg (invalid shared segment parameter)'.
(Details: serial 30 error_code 172 request_code 149 minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
Running it with --sync yields an immediate seg fault:
fbhjr@achilles:~$ /usr/lib/mozilla-firefox/firefox-bin --sync
Segmentation fault (core dumped)
Running gdb on the core shows many symbols being loaded, and then:
Loaded symbols for /usr/lib/mozilla-firefox/components/libnsappshell.so
#0 0x4118a780 in raise () from /lib/tls/libpthread.so.0
In gdb (running with --sync):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1075354752 (LWP 5139)]
0x40497276 in ?? () from
#0 0x40497276 in ?? ()
#1 0x080d0710 in ?? ()
#2 0x080b5780 in ?? ()
#3 0x00000000 in ?? ()
#4 0x401031b5 in nsComponentManagerImpl::~nsComponentManagerImpl ()
#5 0x0804ed06 in ScopedXPCOMStartup::SetWindowCreator ()
#6 0x080510be in xre_main ()
#7 0x0804c803 in main ()
I wanted to ask here first for some advice/clue before perhaps posting this
as a bug.
Do I need to rebuild this with debugging symbols, as I presume it is
stripped? I am a complete neophyte when it comes to debugging.
As I said above, the behavior is erratic, unpredictable. Certain sites
work fine, while on others it crashes.
Any suggestions would be appreciated.
Fred Henry, Jr.