* thread.c (free_thread): Do not delete the step resume breakpoint

right away.
This commit is contained in:
Daniel Jacobowitz 2007-09-10 21:27:23 +00:00
parent 4eb0ad19f3
commit 4d8453a549
2 changed files with 9 additions and 2 deletions

View File

@ -1,3 +1,8 @@
2007-09-10 Daniel Jacobowitz <dan@codesourcery.com>
* thread.c (free_thread): Do not delete the step resume breakpoint
right away.
2007-09-10 Daniel Jacobowitz <dan@codesourcery.com>
* arch-utils.c (gdbarch_info_fill): Also try core_bfd.

View File

@ -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? */