[Bug gdb/17283] gdbserver stops working in non-stop mode

["dje at google dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17283

--- Comment #3 from dje at google dot com ---
(In reply to dje from comment #2)
> Re:
> >The same question, about removal off breakpoints, upon unpleasent sitatuations >are recognized: when it happens that gdb offers to write down its core dump, does >it remove all inserted breakpoints and leave the process running furhter?
> 
> I can't find any code that does this.
> Easy enough to verify of course.

Yeah, simple experiment confirms that breakpoints aren't removed before gdb
terminates.

One issue that needs to be taken into account is that when we're in this
situation, gdb has detected an internal error - trying to do anything has no
guarantees of success.  On can certainly wish gdb would try though.

[Note to self:
If gdb is going to exit after dumping core (including letting the generation of
the core dump cause the exit, e.g., SIGABRT), it currently doesn't fork().
If we do try to clean up before we generate a core dump we'll want to fork() in
order to have the coredump more accurately represent gdb's state at the time of
internal-error detection.]

-- 
You are receiving this mail because:
You are on the CC list for the bug.