I tried to get a stacktrace with gdb. I attached gdb to the running
process of gnome-settings-daemon by using a startup-script that
contained the following lines:
gdb -batch-silent \
-ex 'set logging overwrite on' \
-ex "set logging file /tmp/gdb-gsd-${RANDOM}.txt" \
-ex 'set logging on' \
-ex 'handle SIG33 pass nostop noprint' \
-ex 'set pagination 0' \
-ex "attach ${pid}" \
-ex 'continue' \
-ex 'backtrace full' \
-ex 'info registers' \
-ex 'x/16i $pc' \
-ex 'thread apply all backtrace' \
-ex 'quit' \
< /dev/null
When gnome-settings-daemon crashed, the output was as follows:
[Thread debugging using libthread_db enabled]
[New Thread 0xb748db70 (LWP 1861)]
[Thread 0xb748db70 (LWP 1861) exited]
Program exited with code 01.
No stack.
The program has no registers now.
No registers.
Unfortunately there is still no stacktrace. Did I miss something on
using gdb?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588155
Title:
randomly gnome-settings-daemon fails to start
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
