Fix removal of temporary breakpoints when rapidly restarting thread

This bug would occur when the debugger keeps rapidly hitting a
breakpoint and restarting execution (and the breakpoint is temporary /
one-time).  For example, stepping over a long recursive call.

It would be possible for the user to manually interrupt execution at the
precise moment that the debugee was returning from a single step over
the breakpoint.  In this scenario, the thread would correctly remain
stopped as requested, however the temporary breakpoint would incorrectly
remain in the breakpoint list.  The cause of this issue is that
uninstall_breakpoints only considered removing temporaries if they were
currently installed for use.

This makes sense, as we have used the b->installed flag as a sort of
check to see if we have YET installed the breakpoint (rather than "is it
STILL installed?") to ensure that we don't remove it too soon.

The more accurate logic here is to acctually check whether the
breakpoint has EVER been installed and only then consider it for removal
if it is temporary.  This fixes the case in question without breaking
behavior when performing an initial run single step.

Signed-off-by: Malfurious <m@lfurio.us>

1 files changed, 1 insertions, 0 deletions

diff --git a/debugger.h b/debugger.h
index cea3bba..f14459f 100644
--- a/debugger.h
+++ b/debugger.h
@@ -11,6 +11,7 @@ struct breakpoint {
     unsigned long address;
     unsigned long text;
     int installed;
+    int previously_installed;
     int hits;
     int user;