[Bug breakpoints/11669] New: would like some kind of non-stopping breakpoint

["tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

>From http://sourceware.org/gdb/wiki/2009_GCC_Summit_BoF, but
I've also had this reported to me directly:

IWBN: Would like to do "stuff" when the program goes through a specific location
in the code. For instance, print a trace every time some code is executed.
Cannot use breakpoint and an associated command list because there is no way to
resume the execution as if the breakpoint was never hit. for instance, one
cannot use "continue" in the commands list, because the breakpoint might have
been hit while doing a "next".

One response, also from the above link:

One of the solution discussed would be to have a new possible command that would
resume the previous operation, whatever it was. For instance, if the previous
operation was a "next", then resume the same "next" operation. Then a user could
use a breakpoint commands list and end it with that new command. No discussion
on how actually feasible that is.


Another possible idea would be to give each breakpoint a "disposition",
either "stop" or "continue", then have the infrun logic handle continuing
breakpoints specially somehow.

This feature would also be very useful from Python.

-- 
           Summary: would like some kind of non-stopping breakpoint
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: tromey at redhat dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=11669

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.