[Evolution] Bug#434910: evolution sporadically becomes unresponsive, uses all CPU: help debugging

Ross Boylan ross at biostat.ucsf.edu
Mon Oct 1 17:59:49 UTC 2007


This problem is really making things difficult for me, so I attempted to
debug it.  I have evolution-dbg installed, but something seems to be
missing.  When I attach to the process during one of its high CPU times,
I got messages that it was loading many symbols and then
Reading symbols from /usr/lib/libglade/2.0/libgnome.so...done.
Loaded symbols for /usr/lib/libglade/2.0/libgnome.so
Reading symbols from /usr/lib/libglade/2.0/libbonobo.so...done.
Loaded symbols for /usr/lib/libglade/2.0/libbonobo.so
Failed to read a valid object file image from memory.
0xb7776587 in pthread_mutex_lock () from /lib/i686/cmov/libpthread.so.0
(gdb) where
#0  0xb7776587 in pthread_mutex_lock ()
from /lib/i686/cmov/libpthread.so.0
#1  0xb6ef1a00 in g_signal_handlers_block_matched ()
from /usr/lib/libgobject-2.0.so.0
#2  0xb64b6a10 in emft_model_row_changed (model=0x8119008,
path=0xa6d83d0, iter=0xb5bd428, emft=0xa2568b0) at em-folder-tree.c:1865
#3  0xb75492dd in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#4  0x08119008 in ?? ()
#5  0x0a6d83d0 in ?? ()
#6  0x0b5bd428 in ?? ()
#7  0x0a2568b0 in ?? ()
#8  0x00000001 in ?? ()
#9  0x0000006e in ?? ()
#10 0x08119008 in ?? ()
#11 0xb6f0a678 in ?? () from /usr/lib/libgobject-2.0.so.0
#12 0xb7549280 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0xffffffff in ?? ()
#14 0xbfe869f8 in ?? ()
#15 0xb6eda722 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Backtrace stopped: frame did not save the PC

I did gdb on /usr/bin/evolution.

Can anyone help me get something better?  The oddities I notice are
1. "Failed to read a valid object file image from memory."  Maybe this
refers to the main binary, and that's why I don't see many symbols?
2. lots of missing symbolic info on the stack.
3. "Backtrace stopped: frame did not save the PC"

BTW I'm currently unable to build from the source on my machine becausee
the build-dependencies required seem to knock out too much.





More information about the Pkg-evolution-maintainers mailing list