Re: Internal breakpoints

Jim Blandy
2003-10-01T06:45:12Z

ankit thukral <ankit_plug@yahoo.com> writes:
> -2 shlib events keep y 0x4000c9c0
> <_dl_debug_state_internal>
> breakpoint already hit 3 times

The dynamic linker in the program being debugged calls this function
each time it loads or unloads a shared library. GDB sets this
breakpoint so it can keep its copy of the shared library table up to
date.

> -7 longjmp keep n 0x4000f870 <longjmp>
> -8 longjmp keep n 0x42027240 <siglongjmp>
> -9 longjmp keep n 0x42027240 <siglongjmp>
> -10 longjmp resume keep n 0x00000000

GDB needs to be able to recognize calls to longjmp, to avoid losing
control of the program, to make sure watchpoints on local variables in
frames popped by the longjmp are disabled, and so on.

You'll need to look at breakpoint.c for more detail.