From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB's breakpoint internals
Date: Wed, 26 Mar 2003 00:35:00 -0000 [thread overview]
Message-ID: <20030326003536.GA14672@nevyn.them.org> (raw)
In-Reply-To: <3E80F4DF.4090809@redhat.com>
On Tue, Mar 25, 2003 at 07:31:27PM -0500, Andrew Cagney 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.
Yes. If someone volunteers to do something about it...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-26 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 0:31 Andrew Cagney
2003-03-26 0:35 ` Daniel Jacobowitz [this message]
2003-03-26 4:28 ` Eli Zaretskii
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=20030326003536.GA14672@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.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