* GDB's breakpoint internals
@ 2003-03-26 0:31 Andrew Cagney
2003-03-26 0:35 ` Daniel Jacobowitz
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cagney @ 2003-03-26 0:31 UTC (permalink / raw)
To: gdb
(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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GDB's breakpoint internals
2003-03-26 0:31 GDB's breakpoint internals Andrew Cagney
@ 2003-03-26 0:35 ` Daniel Jacobowitz
2003-03-26 4:28 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Jacobowitz @ 2003-03-26 0:35 UTC (permalink / raw)
To: Andrew Cagney; +Cc: gdb
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: GDB's breakpoint internals
2003-03-26 0:35 ` Daniel Jacobowitz
@ 2003-03-26 4:28 ` Eli Zaretskii
0 siblings, 0 replies; 3+ messages in thread
From: Eli Zaretskii @ 2003-03-26 4:28 UTC (permalink / raw)
To: drow; +Cc: ac131313, gdb
> Date: Tue, 25 Mar 2003 19:35:36 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> >
> > 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...
...or at least to document how it's done now...
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-03-26 4:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-26 0:31 GDB's breakpoint internals Andrew Cagney
2003-03-26 0:35 ` Daniel Jacobowitz
2003-03-26 4:28 ` Eli Zaretskii
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox