This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
GDB's breakpoint internals
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 25 Mar 2003 19:31:27 -0500
- Subject: GDB's breakpoint internals
(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