[Bug server/16801] New: can't attach in async/non-stop, plus subsequent gdbserver assert failure on reconnect

[Bug server/16801] New: can't attach in async/non-stop, plus subsequent gdbserver assert failure on reconnect

[dje at google dot com]

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

            Bug ID: 16801
           Summary: can't attach in async/non-stop, plus subsequent
                    gdbserver assert failure on reconnect
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Created attachment 7522
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7522&action=edit
testcase for repro

bash1$ ./forever-threads.x64 >&foo.log &
13595
bash1$ gdbserver-devel --multi :1234

bash2$ gdb-devel forever-threads.x64
(gdb) tar ext :1234
(gdb) set target-async on
(gdb) set non-stop on
(gdb) attach 13595
Attaching to program: /home/dje/src/play/forever-threads.x64, process 13595
Attaching to process 13595 failed with:
T0006:ffffffff00000000;07:20ea7501ff7f0000;10:ddb064b1707f0000;thread:p351b.351b;core:6;
(gdb) tar ext :1234
Already connected to a remote target.  Disconnect? (y or n) y

Remote debugging using :1234
Remote connection closed
(gdb) 

The second connection to gdbserver causes:

../../../trunk/gdb/gdbserver/server.c:2696: A problem internal to GDBserver has
been detected.
queue_stop_reply_callback: Assertion `thread->last_status.kind !=
TARGET_WAITKIND_IGNORE' failed.

So there are (at least) two bugs here:
1) How come the attach failed?
1b) Seems like gdbserver should be detached from the inferior at this point.
2) gdbserver crash

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

[Bug server/16801] can't attach in async/non-stop, plus subsequent gdbserver assert failure on reconnect

[dje at google dot com]

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

--- Comment #1 from dje at google dot com ---
If I do the set target-async/non-stop on before "tar ext :1234" then the attach
works.  Not unexpected, per se, but I think gdb could be more friendly here.

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