[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

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at google dot com

--- Comment #2 from dje at google dot com ---
I agree more clarity is needed here, but first some data points.

Re:
>Moreover, I expect that target remote can be run async:
>  target remote   -- stops the program, after connecting to remove
>  target remote & -- doesn't stop the program (implies continue&)

"target remote ... &" is not, AIUI, expected to do what you think it does.
IOW, "&" has no special meaning to "target remote".
[One could entertain the thought of extending "target ..." to handle "&",
but that's a separate subject.  There are already existing ways to handle
some things, so the additional complexity would need to be justified.]

"target remote" just establishes a connection with gdbserver,
it does not affect the running state of an inferior.

Re:
>Does gdbserver in fact interrupt the program, when attaching to it, before gdb >connects to it over target remote?

Yes it does.

If one wants to attach to a running program, and leave it running, one
generally
uses "target extended-remote ..." and then "attach ... &" from gdb.

Re:
>Finally, when gdbserver is aware, that it is going to terminate abnormally, [...]
>does gdbserver remove all breakpoints?

Depending on what form of breakpoint is being used, gdbserver may not even be
aware that breakpoints have been asserted.  No disagreement that we should be
removing breakpoints, just a note to say this will take a bit of cooperation
with gdb (to fully handle all possible cases).  For a start, gdbserver could at
least remove the ones it is aware of.

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.

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