On Fri, Jun 5, 2009 at 7:29 AM, Patrick Ohly wrote:
> On Thu, 2009-06-04 at 10:07 -0700, David L wrote:
>> My fedora 11 evolution just hung for the second time
>> today. This time I used gdb to get the following backtrace.
>> Not sure if it's useful:
>
> Better use "thread apply all bt". That'll g
On Thu, 2009-06-04 at 10:07 -0700, David L wrote:
> My fedora 11 evolution just hung for the second time
> today. This time I used gdb to get the following backtrace.
> Not sure if it's useful:
Better use "thread apply all bt". That'll give information about all
active threads and perhaps show a
On Thu, 2009-06-04 at 10:07 -0700, David L wrote:
> My fedora 11 evolution just hung for the second time
> today. This time I used gdb to get the following backtrace.
Please report this to http://bugzilla.gnome.org under the Evolution Mail
component, with a description of what you were doing when
My fedora 11 evolution just hung for the second time
today. This time I used gdb to get the following backtrace.
Not sure if it's useful:
#0 0x002d5422 in __kernel_vsyscall ()
#1 0x00311fa5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2 0x05006ccb in giop_recv_buffer_get (e
