From: Jim Ingham <jingham@apple.com>
To: gdb@sources.redhat.com
Subject: Re: gdb Digest 26 Mar 2003 19:03:48 -0000 Issue 1129
Date: Wed, 26 Mar 2003 19:37:00 -0000 [thread overview]
Message-ID: <672C9F08-5FC2-11D7-B2F4-00039379E320@apple.com> (raw)
In-Reply-To: <1048705428.15342.ezmlm@sources.redhat.com>
Andrew,
Addressing this problem - driven by the needs of C++ developers - is
something I was lobbying for time to do during this release cycle. But
it got put off in favor of solving performance issues in gdb instead.
However, for the next one (starting post June) release cycle I will
probably get more time to look at this.
I don't think we can just hide the physical breakpoints from the user
however. It would be very useful to be able to say
(gdb) break FileFullOfTemplates.cc:27
then decide that "no you weren't interested in the int specialization
only the double one", or whatever... So being able to peer into the
contents of the user-lever breakpoint is a good thing. OTOH, I should
certainly be able to disable this breakpoint and not hit it for any
variant...
Jim
On Wednesday, March 26, 2003, at 11:03 AM,
gdb-digest-help@sources.redhat.com wrote:
>
> (Put simply, the things you learn when reading a book explaining how a
> debugger should work :-)
>
> The `How Debuggers Work' [rosenberg] book describes a breakpoint
> implementation broken into two parts:
>
> - high level user breakpoint list
> This is what the user sees. One entry corresponds to each `break XXX'
> command. That high level breakpoint then maps onto 1 or more ...
>
> - low level physical breakpoints (or watchpoints or ...)
> One entry per physical breakpoint. When a breakpoint is hit, a
> reverse map back to each high-level breakpoint for the event is done,
> and then that breakpoint's handler is called.
>
> I might be mistaken, but I don't think GDB implemented things this
> way. Instead, it has a single tangled table.
>
> Andrew
>
>
--
Jim Ingham jingham@apple.com
Developer Tools
Apple Computer
next parent reply other threads:[~2003-03-26 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1048705428.15342.ezmlm@sources.redhat.com>
2003-03-26 19:37 ` Jim Ingham [this message]
2003-03-28 22:49 ` Andrew Cagney
2003-03-28 23:13 ` Andrew Cagney
2003-03-28 23:56 ` Daniel Jacobowitz
2003-03-29 0:49 ` Andrew Cagney
2003-03-29 0:58 ` Daniel Jacobowitz
2003-03-29 1:32 ` Andrew Cagney
2003-03-29 3:30 ` Jim Ingham
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=672C9F08-5FC2-11D7-B2F4-00039379E320@apple.com \
--to=jingham@apple.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).