diff options
| author | Jason Molenda <jmolenda@apple.com> | 1999-08-23 22:40:00 +0000 |
|---|---|---|
| committer | Jason Molenda <jmolenda@apple.com> | 1999-08-23 22:40:00 +0000 |
| commit | 53a5351d907ef4eacd463a48a86d35b2b70b9f60 (patch) | |
| tree | 22c35199ec70962e33c63d2111f333bfdcce02e1 /gdb/infrun.c | |
| parent | 093505ad6138b9e165876765ecd667c90fc921ae (diff) | |
| download | gdb-53a5351d907ef4eacd463a48a86d35b2b70b9f60.zip gdb-53a5351d907ef4eacd463a48a86d35b2b70b9f60.tar.gz gdb-53a5351d907ef4eacd463a48a86d35b2b70b9f60.tar.bz2 | |
import gdb-1999-08-23 snapshot
Diffstat (limited to 'gdb/infrun.c')
| -rw-r--r-- | gdb/infrun.c | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/gdb/infrun.c b/gdb/infrun.c index 0ddb8f2..a227c7a 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -1285,8 +1285,9 @@ init_execution_control_state (struct execution_control_state *ecs) } /* Call this function before setting step_resume_breakpoint, as a - sanity check. We should never be setting a new - step_resume_breakpoint when we have an old one active. */ + sanity check. There should never be more than one step-resume + breakpoint per thread, so we should never be setting a new + step_resume_breakpoint when one is already active. */ static void check_for_old_step_resume_breakpoint (void) { @@ -2289,7 +2290,12 @@ handle_inferior_event (struct execution_control_state *ecs) If we reach here and step_resume_breakpoint is already NULL, then apparently we have multiple active step-resume bp's. We'll just delete the breakpoint we - stopped at, and carry on. */ + stopped at, and carry on. + + Correction: what the code currently does is delete a + step-resume bp, but it makes no effort to ensure that + the one deleted is the one currently stopped at. MVS */ + if (step_resume_breakpoint == NULL) { step_resume_breakpoint = |