[Bug gdb/27084] New: Setting non-stop after connecting to extended remote target screw things up

[Bug gdb/27084] New: Setting non-stop after connecting to extended remote target screw things up

[simark at simark dot ca]

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

            Bug ID: 27084
           Summary: Setting non-stop after connecting to extended remote
                    target screw things up
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

In terminal 1:

$ ../gdbserver/gdbserver --once --multi :1234

In terminal 2:

$ ./gdb -q -nx --data-directory=data-directory a.out  -ex "tar ext :1234" -ex
"set remote exec-file /home/smarchi/build/wt/test/gdb/a.out" -ex "set non-stop
on"
Reading symbols from a.out...
Remote debugging using :1234
(gdb) r
Starting program: /home/smarchi/build/wt/test/gdb/a.out 
Reading /lib64/ld-linux-x86-64.so.2 from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to
access files locally instead.
Reading /lib64/ld-linux-x86-64.so.2 from remote target...
Reading /lib64/ld-2.31.so from remote target...
Reading /lib64/.debug/ld-2.31.so from remote target...
Reading /usr/lib/debug//lib64/ld-2.31.so from remote target...
Reading /usr/lib/debug/lib64//ld-2.31.so from remote target...
Reading target:/usr/lib/debug/lib64//ld-2.31.so from remote target...
Unexpected vCont reply in non-stop mode:
T05swbreak:;06:60e1ffffff7f0000;07:70dfffffff7f0000;10:a537fdf7ff7f0000;thread:pdf808.df808;core:d;

When we connect to the remote (tar ext :1234), we send QNonStop:0, because
non_stop is off at that time.  The "set non-stop on" succeeds, because no
target has execution.  From this point, the remote target thinks it is in
non-stop mode (because it checks the non_stop global) while gdbserver works in
all-stop mode.

When the remote target sends a vCont;c, it expects to receive "ok" (as expected
in non-stop mode).  But the stop reports a stop reply (as expected in all-stop
mode), and we get this error above.

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