Bug#576813: Acknowledgement (xserver-xorg-core: xserver locks up when gdb attaches to it)
Debian Bug Tracking System wrote, on 07/04/10 22:21:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Debian X Strike Force<debian-x@lists.debian.org>
If you wish to submit further information on this problem, please
send it to 576813@bugs.debian.org.
Please do not send mail to owner@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
The problem seems to be (as pointed out to me in #radeon on freenode):
"note that gdb always stops execution of the process it attaches to...
that's not a 'lockup', just enter 'continue'"
The instructions at
http://wiki.debian.org/XStrikeForce/XserverDebugging
seem to omit this. The word "continue" should probably be added after
"set logging on" and before "bt full" with some indication of performing
the action known to cause the problem.
Obtaining a backtrace with gdb
Please read this section entirely before actually trying to attach a gdb
Note that you must have root permissions (either running as root or
using sudo) to do the following. Attaching gdb to X server before
reproducing the crash might catch a nice backtrace:
gdb -p $(pidof X)
(inside gdb)
set logging overwrite on
set logging on
bt full
set logging off
quit
After this, you get the gdb output in file /etc/X11/gdb.txt (this is
what the logging commands did, another solution is to copy-paste the
output yourself). Add all this to your bug report, developers will
appreciate it. If the backtrace is small, you probably miss several
debugging packages, see above.
Reply to: