Bug#739580: backtrace

[Wendy J. Elmer]

When I run gnome-system-monitor in a debugger and do an interrupt after
gnome-system-monitor takes 100% cpu and does not start, a backtrace
gives the following:

#0  __GI___pthread_mutex_lock (mutex=0x7ffff7ffd968 <_rtld_global+2312>)
at ../nptl/pthread_mutex_lock.c:70
#1  0x00007ffff7dde079 in tls_get_addr_tail (ti=0x7fffef87ef68,
dtv=0x7ffff7fa0310, the_map=0x7ffff7fb34e8) at dl-tls.c:722
#2  0x00007fffef67239e in ?? ()
from /lib/x86_64-linux-gnu/libselinux.so.1
#3  0x00007fffef672622 in ?? ()
from /lib/x86_64-linux-gnu/libselinux.so.1
#4  0x000000000042e649 in get_process_selinux_context(ProcInfo*) ()
#5  0x0000000000421118 in ProcInfo::ProcInfo(int) ()
#6  0x0000000000421d69 in proctable_update(GsmApplication*) ()
#7  0x000000000041ae90 in update_page_activities(GsmApplication*) ()
#8  0x000000000041c084 in create_main_window(GsmApplication*) ()
#9  0x0000000000432d78 in GsmApplication::on_startup() ()
#10 0x00007ffff6dbc32d in
Gio::Application_Class::startup_callback(_GApplication*) ()
from /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
#11 0x00007ffff49175e7 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff4930088 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007ffff4930ce2 in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007ffff5592b5a in g_application_register ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x00007ffff55932c7 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#16 0x00007ffff6dbbe17 in
Gio::Application::local_command_line_vfunc(char**&, int&) ()
from /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
#17 0x00007ffff6dbc52b in
Gio::Application_Class::local_command_line_vfunc_callback(_GApplication*, char***, int*) () from /usr/lib/x86_64-linux-gnu/libgiomm-2.4.so.1
#18 0x00007ffff55935ab in g_application_run ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#19 0x0000000000419c1b in main ()

I can continue and interrupt as many times as I want and the program
will always be in the tls_get_addr_tail function.  I am not running a
version with symbols so I can't actually step through it and see what it
is looping on.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20140410/e823d867/attachment.html>