From: Daniel Jacobowitz <drow@false.org>
To: Michael FIG <michael-dated-1177036471.79d946@fig.org>
Cc: gdb@sourceware.org
Subject: Re: debugging a program that uses SIGTRAP
Date: Wed, 21 Mar 2007 11:14:00 -0000 [thread overview]
Message-ID: <20070321111421.GB27561@caradoc.them.org> (raw)
In-Reply-To: <7qtzwfuxxk.fsf@babe.fig.org>
On Tue, Mar 20, 2007 at 08:34:31PM -0600, Michael FIG wrote:
> > I don't see any good way to solve this. You've got two sets of
> > breakpoints and they're both going to stop GDB - it doesn't know which
> > ones you want and which you don't.
>
> Okay. I thought somehow GDB would pass SIGTRAP iff it knows it has
> not set a breakpoint on the current instruction pointer by scanning
> its list of breakpoints.
You've asked it to pass all SIGTRAPs and it's doing what you said -
I think you're stuck. However, it might be possible to make it do
this. The logic is in infrun.c. Be careful; that's one of the
touchiest pieces of GDB.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-21 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 2:06 Michael FIG
2007-03-21 2:18 ` Daniel Jacobowitz
2007-03-21 2:34 ` Michael FIG
2007-03-21 11:14 ` Daniel Jacobowitz [this message]
2007-03-23 4:30 ` Michael FIG
2007-03-21 14:14 ` Joel Brobecker
2007-03-21 18:51 ` Michael Snyder
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=20070321111421.GB27561@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=michael-dated-1177036471.79d946@fig.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