Comment 12 for bug 373842

When I do this it locks up when I switch to calendar.

 Here is what I get

(gdb) continue
Continuing.
[New Thread 0xb63a8b90 (LWP 4251)]
Cannot get thread event message: debugger service failed
(gdb) backtrace
#0 0xb7ef2430 in __kernel_vsyscall ()
#1 0xb73b6ae7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb74e774b in g_poll () from /usr/lib/libglib-2.0.so.0
#3 0xb74d9f82 in ?? () from /usr/lib/libglib-2.0.so.0
#4 0xb74da5ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5 0xb7710cc3 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#6 0x0804b96c in ?? ()
#7 0xb72f3775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#8 0x0804a421 in ?? ()

Sebastien Bacher wrote:
> the log you got shows it's eds crashing and not evolution
>
> the way to get a stacktrace is either to use apport or gdb this way
>
> - start evolution on the email component
> - gdb --pid `pidof evolution-data-server-2.26`
> (gdb) continue
> - switch evolution to the calendar
> - the gdb prompt will be stopped on the e-d-s crash
> (gdb) backtrace
>
>