public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13860] Different sync vs async MI output
Date: Thu, 22 May 2014 10:55:00 -0000 [thread overview]
Message-ID: <bug-13860-4717-W9LzVqkY92@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13860-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13860
--- Comment #15 from Pedro Alves <palves at redhat dot com> ---
I have a WIP patch for that.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-05-22 10:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 8:12 [Bug testsuite/13860] New: Fail in gdb.mi/mi-solib.exp when displaced stepping is on qiyao at gcc dot gnu.org
2012-03-16 10:14 ` [Bug testsuite/13860] " palves at redhat dot com
2012-03-16 10:46 ` [Bug testsuite/13860] Fail in gdb.mi/mi-solib.exp in async mode qiyao at gcc dot gnu.org
2012-03-16 10:53 ` palves at redhat dot com
2012-05-08 13:17 ` qiyao at gcc dot gnu.org
2012-05-08 13:22 ` palves at redhat dot com
2012-05-08 14:15 ` qiyao at gcc dot gnu.org
2012-05-08 14:25 ` palves at redhat dot com
2012-05-08 14:40 ` qiyao at gcc dot gnu.org
2012-05-09 8:04 ` qiyao at gcc dot gnu.org
2012-05-09 14:51 ` [Bug gdb/13860] " palves at redhat dot com
2012-05-09 17:25 ` palves at redhat dot com
2014-05-21 22:17 ` cvs-commit at gcc dot gnu.org
2014-05-21 22:36 ` cvs-commit at gcc dot gnu.org
2014-05-21 22:43 ` palves at redhat dot com
2014-05-22 10:54 ` [Bug gdb/13860] Different sync vs async MI output palves at redhat dot com
2014-05-22 10:55 ` palves at redhat dot com [this message]
2014-05-29 12:16 ` cvs-commit at gcc dot gnu.org
2014-05-29 12:46 ` palves at redhat 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-13860-4717-W9LzVqkY92@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).