On Fri, 14 Apr 2000 00:31:28 -0700,
George Anzinger <george@pioneer.net> wrote:
>This of course, leads one to question if gdb removes and reinstalls
>breakpoints
>as it switches between waiting for the keyboard and waiting for the next
>breakpoint to be hit. Usually debuggers do this to make the breakpoint
>disapear to those who would list the code or otherwise examine memory.
>Anyone know what gdb does?
When gdb hits a breakpoint, one of the things it does before returning
control to the user is to remove all breakpoints. This lets multi
threaded applications like the kernel continue their processing while
the user thinks about whet to type next. gdb assumes that code does
not mutate underneath it, not a valid assumption for __init code.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:09 EST