I've struggled to get a backtrace as gdb hangs when using it against a
running gnome-settings-daemon PID (not even responding to Ctrl+C), but
when killing all running gnome-settings-daemon processes and then
starting gdb with a new gnome-settings-daemon process, I got the
following results:

GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/gnome-settings-daemon...(no debugging symbols 
found)...done.
(gdb) handle SIG33 pass nostop noprint
Signal        Stop      Print   Pass to program Description
SIG33         No        No      Yes             Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gnome-settings-daemon 
[Thread debugging using libthread_db enabled]

** At this point, I added a new keyboard layout to the Keyboard
Preferences dialogue and the CPU usage went up to 100% until I removed
the new layout. I then executed 'killall gnome-settings-daemon' from a
terminal.

Program exited normally.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb)

** At this point, after realising that gdb didn't seem to have picked anything 
up, I added a new keyboard layout again in the Keyboard Preferences dialogue. 
The CPU usage went up to 100% and the following two lines were output from gdb:
 
(gnome-settings-daemon:25101): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: 
assertion `dest_width > 0' failed

(gnome-settings-daemon:25101): GLib-GObject-CRITICAL **: g_object_unref:
assertion `G_IS_OBJECT (object)' failed


** After this I attempted to use Ctrl+C to kill the process inside gdb, but at 
this point gdb hung and I was unable to continue debugging. I hope the above 
two lines are of some use. Please inform me of how I might be able to generate 
a proper stack trace if not.

-- 
Adding additional keyboard layouts causes gnome-settings-daemon to use max CPU
https://bugs.launchpad.net/bugs/587228
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to