From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/mi: fix breakpoint script field output
Date: Thu, 26 May 2022 12:10:48 -0600 [thread overview]
Message-ID: <875yls6u6v.fsf@tromey.com> (raw)
In-Reply-To: <20220504121342.1208374-1-simon.marchi@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Wed, 4 May 2022 08:13:42 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> The "script" field, output whenever information about a breakpoint with
Simon> commands is output, uses wrong MI syntax.
I think this is PR mi/24285.
Simon> Fix it, keeping the backwards compatibility by introducing a new MI
Simon> version (MI4), in exactly the same way as was done when fixing
Simon> multi-locations breakpoint output in [2].
Simon> - Add a fix_breakpoint_script_output uiout flag. MI uiouts will use
Simon> this flag if the version is >= 4.
I was under the impression that MI version 3 was somehow experimental,
so we didn't need version 4 yet. But maybe the idea is to roll out new
MI versions with some regularity and just update the version whenever we
think we've made a breaking change?
Tom
next prev parent reply other threads:[~2022-05-26 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:13 Simon Marchi
2022-05-26 18:10 ` Tom Tromey [this message]
2022-05-26 18:21 ` Simon Marchi
2022-08-10 19:38 ` Simon Marchi
2022-08-11 11:56 ` Tom de Vries
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=875yls6u6v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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).