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

["dilyan.palauzov at aegee dot org" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #1 from dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee dot org> ---
Does gdbserver in fact interrupt the program, when attaching to it, before gdb
connects to it over target remote?  I think so, after doing some experiments.

I cannot find the documentation of this behaviour and it is non-intuitive.  But
in such case, the remark above that "target remote &" shall not interrupting
the process, contrary to "target remote" gets irrelevant, as the process is
already interrupted when gdbserver attaches to it.

Moreover, the documentation of gdbserver, option --debug-format offers three
possibilities: none, all, timestamps.  But the documenation does not say, which
of it is valid, if no --debug-format is specified, only --debug .  (Even if
some intermediate loggin level is used, when only --debug without
--debug-format is supplied, this shall also be written down).

Finally, when gdbserver is aware, that it is going to terminate abnormally,
(e.g. by printing

../../../gdb-7.8/gdb/gdbserver/server.c:2695: A problem internal to GDBserver
has been detected.

) does gdbserver remove all breakpoints?  My process, which I debug remotely,
crashes from time time, printing "Trace/breakpoint trap (core dumped)" and I
have never seen this, before doing remote debugging on it.  (This happened
several times, but right now I cannot say how to reproduce it.  Maybe we can
explain this phenomena without further details regarding reproducibility).

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?

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