Re: Galeon crashes

> I believe that the command you want in gdb is "thread apply all bt full"
> that will print out the full backtrace. Your best bet is to start
> galeon, then attach gdb to it, then when it crashes type that command
> in.

OK, now i tried it the way you described... new output looks like this:

Thread 7 (Thread 1082132832 (LWP 15255)):
#0  0x00002aaaae1ba870 in poll () from /lib/libc.so.6
No symbol table info available.
#1  0x00002aaaab11249f in PR_Poll () from /usr/lib/libnspr4.so
No symbol table info available.
#2  0x00002aaab0fbe5d6 in NSGetModule () from 
/usr/lib/mozilla/components/libnecko.so
No symbol table info available.
#3  0x00002aaaaad791cc in nsThread::Main () from 
/usr/lib/mozilla/libxpcom.so
No symbol table info available.
#4  0x00002aaaab113a34 in PR_Select () from /usr/lib/libnspr4.so
No symbol table info available.
#5  0x00002aaaab22db1c in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#6  0x00002aaaae1c3c22 in clone () from /lib/libc.so.6
No symbol table info available.
#7  0x0000000000000000 in ?? ()
....


Does this help better?


best regards,
sigi.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click