summaryrefslogtreecommitdiff
path: root/gdb/thread.c
diff options
context:
space:
mode:
authorDaniel Jacobowitz <dan@debian.org>2007-09-10 21:27:23 +0000
committerDaniel Jacobowitz <dan@debian.org>2007-09-10 21:27:23 +0000
commit67cc72a0248ec8a259bd0057ba5171ce4a9d6fd4 (patch)
tree0d34d98985322fc67b92fcf9f2e62a2a6a2eb2df /gdb/thread.c
parentf17c84c2b78d6fde4bba0660c5962fbd3bba573a (diff)
downloadgdb-67cc72a0248ec8a259bd0057ba5171ce4a9d6fd4.tar.gz
* thread.c (free_thread): Do not delete the step resume breakpoint
right away.
Diffstat (limited to 'gdb/thread.c')
-rw-r--r--gdb/thread.c6
1 files changed, 4 insertions, 2 deletions
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? */