[sylpheed:32037] Re: Sylpheed 2.0 crashes

[Paul]

On Wed, 16 Jan 2008 13:10:25 -0600
Rich Coe <Richard.Coe at med.ge.com> wrote: 

>     You need to start sylpheed and attach to it with the gdb debugger,
>     	gdb -p PID
>     where PID is the process identifier of sylpheed.
>     After attaching with gdb, type the 'c' command for continue.
> 
>     Then do whatever you do in sylpheed to cause it to crash.
>     Go back to the gdb screen, and type 'bt' command for back trace.

Probably easier to do

gdb
file /usr/bin/sylpheed
run --debug
[CRASH]
bt full

best regards

Paul


-- 
It isn't worth a nickle to two guys like you or me, 
but to a collector it is worth a fortune