public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/16801] New: can't attach in async/non-stop, plus subsequent gdbserver assert failure on reconnect Date: Wed, 02 Apr 2014 19:46:00 -0000 [thread overview] Message-ID: <bug-16801-4717@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2014-04-02 19:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-02 19:46 dje at google dot com [this message] 2014-04-02 19:59 ` [Bug server/16801] " dje at google dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16801-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).