From 4d8453a549892438b635947ed681729674f3566d Mon Sep 17 00:00:00 2001 From: Daniel Jacobowitz Date: Mon, 10 Sep 2007 21:27:23 +0000 Subject: [PATCH] * thread.c (free_thread): Do not delete the step resume breakpoint right away. --- gdb/ChangeLog | 5 +++++ gdb/thread.c | 6 ++++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 1d6d0147e92..17023ec02a9 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2007-09-10 Daniel Jacobowitz + + * thread.c (free_thread): Do not delete the step resume breakpoint + right away. + 2007-09-10 Daniel Jacobowitz * arch-utils.c (gdbarch_info_fill): Also try core_bfd. diff --git a/gdb/thread.c b/gdb/thread.c index 563d18a8afa..b6762e1fcfa 100644 --- a/gdb/thread.c +++ b/gdb/thread.c @@ -84,9 +84,11 @@ static void free_thread (struct thread_info *tp) { /* NOTE: this will take care of any left-over step_resume breakpoints, - but not any user-specified thread-specific breakpoints. */ + but not any user-specified thread-specific breakpoints. We can not + delete the breakpoint straight-off, because the inferior might not + be stopped at the moment. */ if (tp->step_resume_breakpoint) - delete_breakpoint (tp->step_resume_breakpoint); + tp->step_resume_breakpoint->disposition = disp_del_at_next_stop; /* FIXME: do I ever need to call the back-end to give it a chance at this private data before deleting the thread? */ -- 2.30.2