Pending Breakpoints

If the debugger cannot resolve a breakpoint location you specify to an address in the current debuggee, it will ask whether to create a 'pending' breakpoint.

A pending breakpoint will be re-evaluated every time a shared library is loaded.  If the location can be resolved to an address at one of those times, the pending breakpoint will become a real breakpoint at that address.

The debugger supports the following specific commands for managing the pending breakpoint support.

To create a pending breakpoint, use:

(idb) set breakpoint pending auto

To have a pending breakpoint always set on an unresolved location, use:

(idb) set breakpoint pending on

To have a pending breakpoint never set on an unresolved location, use:

(idb) set breakpoint pending off

To see the state of the pending breakpoint support, use:

(idb) show breakpoint pending

Normal breakpoint operations are valid for pending breakpoints. Pending breakpoints can be enabled, disabled and deleted. A user condition, fitlers or an action list may be assigned to a pending breakpoint. They will remain with the breakpoint when the location is resolved and the pending breakpoint becomes a real one.

This feature is supported in GDB and DBX user interfaces.