From: Stan Shebs <shebs@cygnus.com>
To: gdb@cygnus.com
Subject: Re: Any way to avoid inserting & removing breakpoints?
Date: Thu, 17 Dec 1998 17:39:00 -0000 [thread overview]
Message-ID: <xdaf0m9qnx.fsf@andros.cygnus.com> (raw)
In-Reply-To: <199812150126.RAA24778.cygnus.gdb@jtc.redbacknetworks.com>
jtc@RedBackNetworks.com (J.T. Conklin) writes:
> I finished my breakpoint extensions prototype, and discovered that GDB
> inserts all enabled breakpoints when program execution is resumed, and
> removes them when it regains control.
Yes, this is a "feature". It's pretty well wired into GDB. It might
be possible to make insert_breakpoints() and remove_breakpoints() do
some sort of caching-like thing, but I'm not sure that all target
memory reads know about substituting original code, so you might get
punished when you're doing disassembly or prologue analysis.
Stan
next parent reply other threads:[~1998-12-17 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199812150126.RAA24778.cygnus.gdb@jtc.redbacknetworks.com>
1998-12-17 17:39 ` Stan Shebs [this message]
1998-12-17 20:40 ` Todd Whitesel
1998-12-18 11:15 ` J.T. Conklin
1998-12-14 17:26 J.T. Conklin
1998-12-17 19:20 ` Todd Whitesel
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=xdaf0m9qnx.fsf@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb@cygnus.com \
/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