public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11688] wrap MI commands in python
Date: Thu, 23 Mar 2023 18:04:04 +0000 [thread overview]
Message-ID: <bug-11688-4717-wUQuH4WRZ1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11688-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11688
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Assignee|unassigned at sourceware dot org |tromey at sourceware dot org
--- Comment #9 from Tom Tromey <tromey at sourceware dot org> ---
I have a patch for this.
I think maybe the break-info bugs were fixed as part of the MI upgrades?
Anyway the output seems generally sane to me now and if we do find
other bad spots, we ought to fix those.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-23 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11688-4717@http.sourceware.org/bugzilla/>
2011-08-26 7:08 ` ratmice at gmail dot com
2011-08-26 12:31 ` ratmice at gmail dot com
2011-08-28 10:34 ` tromey at redhat dot com
2011-08-29 21:06 ` ratmice at gmail dot com
2012-01-02 19:44 ` tromey at redhat dot com
2012-01-03 21:59 ` ratmice at gmail dot com
2012-01-06 22:14 ` ratmice at gmail dot com
2012-01-06 22:17 ` ratmice at gmail dot com
2012-01-06 22:18 ` ratmice at gmail dot com
2023-03-23 18:04 ` tromey at sourceware dot org [this message]
2023-03-24 12:11 ` ratmice at gmail dot com
2023-03-24 16:18 ` tromey at sourceware dot org
2023-04-04 17:10 ` tromey at sourceware dot org
2023-05-23 19:48 ` cvs-commit at gcc dot gnu.org
2023-05-24 17:00 ` tromey 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-11688-4717-wUQuH4WRZ1@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).