From: Daniel Jacobowitz <dan@codesourcery.com>
To: Bernie Innocenti <bernie@codewiz.org>
Cc: rms@gnu.org, dclark <dclark@gnu.org>,
gdb@sourceware.org, xorg-devel@lists.x.org
Subject: Re: Debugging X with GDB
Date: Mon, 11 Jan 2010 14:02:00 -0000 [thread overview]
Message-ID: <20100111140155.GD428@caradoc.them.org> (raw)
In-Reply-To: <1263170536.29695.86.camel@giskard>
On Sun, Jan 10, 2010 at 07:42:16PM -0500, Bernie Innocenti wrote:
> <airlied> I think X might change TTY state and piss gdb off
I'd imagine this is it, but it's impossible to tell without debugging
the TTY state.
When you hit ^C, that doesn't necessarily cause anything to happen.
The TTY subsystem sees ^C, and may or may not generate a SIGINT to the
foreground process group depending on the tty settings; try checking
using stty -F, for instance. Then the foreground process group is X,
not GDB; if the SIGINT is blocked or ignored, it won't be delivered,
so GDB can't intercept it at delivery.
Using ^C is not always reliable.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-01-11 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1NSMSM-0000oT-51@fencepost.gnu.org>
2010-01-11 0:42 ` Bernie Innocenti
2010-01-11 14:02 ` Daniel Jacobowitz [this message]
2010-01-11 14:29 ` Jonathan Morton
2010-01-11 15:22 ` Adam Jackson
2010-01-12 10:03 ` Richard Stallman
2010-01-11 20:26 ` [SOLVED] " Bernie Innocenti
[not found] ` <E1NUPod-00026Y-78@fencepost.gnu.org>
[not found] ` <1263243923.2695.72.camel@giskard>
2010-01-12 23:19 ` Richard Stallman
2010-01-14 22:46 ` Bernie Innocenti
2010-01-15 1:48 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100111140155.GD428@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=bernie@codewiz.org \
--cc=dclark@gnu.org \
--cc=gdb@sourceware.org \
--cc=rms@gnu.org \
--cc=xorg-devel@lists.x.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox