From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Pending breakpoints
Date: Thu, 03 Apr 2008 13:25:00 -0000 [thread overview]
Message-ID: <20080403124823.GA16356@caradoc.them.org> (raw)
In-Reply-To: <18420.47315.225382.512236@kahikatea.snap.net.nz>
On Thu, Apr 03, 2008 at 11:00:35PM +1200, Nick Roberts wrote:
> -6 longjmp keep n 0xb7da7be0 <siglongjmp>
> -7 longjmp keep n 0xb7da7be0 <siglongjmp>
> -8 longjmp keep n 0xb7da7be0 <siglongjmp>
Actually this is the one I consider a problem; it's weird that we look
up the symbol name for this. We set breakpoints on longjmp and
_longjmp and siglongjmp just in case they're different. And that
predates your change.
> > Even better would be to discard locations when we shlib_disable a
> > breakpoint, and get rid of the shlib_disable flag. But doing that may
> > require that we get rid of shared libraries when we're supposed to.
>
> Would that `solve' this problem?
I hope so.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-03 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 20:24 Nick Roberts
2008-02-26 21:38 ` Daniel Jacobowitz
2008-03-21 14:46 ` Daniel Jacobowitz
2008-04-03 11:18 ` Nick Roberts
2008-04-03 11:36 ` Andreas Schwab
2008-04-03 13:25 ` Daniel Jacobowitz [this message]
2008-04-03 17:55 ` Vladimir Prus
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=20080403124823.GA16356@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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