This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] Delay deletion of step-resume breakpoints
> Date: Mon, 13 Aug 2007 23:13:32 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: gdb-patches@sourceware.org
>
> > /* 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. */
>
> Makes me suspect this is just a workaround for another bug, the bug
> being that the inferior isn't properly stopped when this code gets
> called.
Actually, I think that's TRT to do in _all_ cases: we are scheduling a
breakpoint delete the next time GDB is in a predictable state to do
that.
That's exactly analogous to what a Posix filesystem does when you
delete a file: if some process has that file open, the file is
scheduled to be deleted when its last handle is closed.
So I think Daniel's patch makes good sense.