Comment 64 for bug 366471

That is exactly what I did. After switching to calendar and the error occurred, gdb never stopped. I let it run for an hour before hitting Ctrl-C. I wish I knew another way to get you a backtrace.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Sebastien Bacher
Sent: Monday, May 11, 2009 2:38 AM
To: Ken Watson (kwatson)
Subject: [Bug 366471] Re: Calendar closed unexpectedly

the calendar quit indicates an e-d-s crash but your recent log shows a manual interruption, could you try doing that
- start your session
- start evolution on the email component
- use gdb as indicated before on e-d-s
- type "continue" on the (gdb) line
- switch to the calendar in evolution or do whatever you usually do to get the error

the gdb command should stop by itself when you run into the error
without you having to Ctrl-C, when it does type "backtrace full" there