Re: Galeon crashes

On Sun, 2006-01-01 at 22:09 +0100, sigi wrote:
> 
> > If you can get a stacktrace, and the first few lines contain entries
> > from libimglib2.so then this is definitely the cause.
> 
> There's nothing about libimglib2.so. 
> This are the first lines: (If I did it right?) 

Not quite, that is the backtrace from just one thread that is stuck in a
pthread condition wait (which is a perfectly valid position to be stuck
in).

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.

HTH

Crispin



-------------------------------------------------------
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