Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* 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

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