Open a shell window and type:
gdb wombat (or the name of the process that died)
At the gdb prompt, type:
(gdb) attach <pid>
where pid is the process Id of the application that just crashed. The
crash dialog box will tell you what the process Id is. Don't close
the crash dialog box until you finish with the backtrace.
Once you attach to the prcess, you should see a bunch of symbols
being loaded. After it is done, type:
(gdb) bt
This produces a backtrace. Record that and send it to the developers.
Detach from the process and quit.
(gdb) detach
(gdb) quit
Ujwal
At 2:47 PM +0200 6/3/2001, michael gruner wrote:
>yes, i'd like to do this, but there's a little problem: i know how to
>compile and use evo, but i've got no idea on how to produce this stack
>trace, Ettore, could you please instruct me, on how to do this, or give
>me a link, where this is discribed ??
>
>thanks
>
>Micha
>Am 03 Jun 2001 03:37:01 -0400 schrieb Ettore Perazzoli:
>> > now trying to sync the contacts with my pilot crashes the wombat
>> > application every time, the calendar and the todo's are synced
>> > perfectly. now there are two questions:
>> >
>> > 1. has anyone an idea what to do ?
>> > 2. if not, how can i debug this ?
>>
>> Can you please provide us with a stack trace for the crash?
>>
>> --
>> Ettore
>>
>> _______________________________________________
>> evolution maillist - [EMAIL PROTECTED]
>> http://lists.helixcode.com/mailman/listinfo/evolution
>
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>_______________________________________________
>evolution maillist - [EMAIL PROTECTED]
>http://lists.helixcode.com/mailman/listinfo/evolution
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution
