public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/15564] MI thread-exited event inconsistency when detaching
Date: Tue, 27 Oct 2015 17:26:00 -0000	[thread overview]
Message-ID: <bug-15564-4717-nan7b6C8Ne@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15564-4717@http.sourceware.org/bugzilla/>

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

Yao Qi <qiyao at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |qiyao at gcc dot gnu.org
         Resolution|FIXED                       |---

--- Comment #3 from Yao Qi <qiyao at gcc dot gnu.org> ---
The test still fails when testing with GDBserver.

-target-detach^M
=thread-group-exited,id="i1"^M
=library-unloaded,id="/lib64/ld-linux-x86-64.so.2",target-name="/lib64/ld-linux-x86-64.so.2",host-name="target:/lib64/ld-linux-x86-64.so.2",thread-group="i1"^M
=library-unloaded,id="/lib/x86_64-linux-gnu/libc.so.6",target-name="/lib/x86_64-linux-gnu/libc.so.6",host-name="target:/lib/x86_64-linux-gnu/libc.so.6",thread-group="i1"^M
^done^M
(gdb) ^M
FAIL: gdb.mi/mi-detach.exp: detach

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


  parent reply	other threads:[~2015-10-27 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 16:05 [Bug mi/15564] New: " simon.marchi at ericsson dot com
2015-06-02 19:34 ` [Bug mi/15564] " cvs-commit at gcc dot gnu.org
2015-06-03 14:18 ` simon.marchi at ericsson dot com
2015-10-27 17:26 ` qiyao at gcc dot gnu.org [this message]
2015-10-27 17:29 ` simon.marchi at ericsson dot com
2024-01-13 20:04 ` ssbssa at sourceware dot org

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-15564-4717-nan7b6C8Ne@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: link
Be 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).