From: Simon Marchi <simark@simark.ca>
To: Simon Marchi <simon.marchi@ericsson.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Fix MI output for multi-location breakpoints
Date: Wed, 13 Mar 2019 19:16:00 -0000 [thread overview]
Message-ID: <5c79a173-d2eb-3e84-5d73-d52b0ec5fe17@simark.ca> (raw)
In-Reply-To: <44a5cfcc-d98e-fd14-ff47-755e218d76d0@ericsson.com>
On 2019-01-21 12:09 p.m., Simon Marchi wrote:
> On 2019-01-18 4:46 p.m., Eli Zaretskii wrote:
>>> From: Simon Marchi <simon.marchi@ericsson.com>
>>> CC: Simon Marchi <simon.marchi@ericsson.com>
>>> Date: Fri, 18 Jan 2019 19:57:11 +0000
>>>
>>> +The following commands can be used to selectively enable behaviors from a
>>> +newer MI version. They can be useful if you want to take advantage of feature
>>> +or bug fix only available in a more recent MI version than what you are using,
>>> +but can't yet migrate to that version for some reason.
>>> +
>>> +@table @code
>>> +
>>> +@item -fix-multi-location-breakpoint-output
>>> +Use the output for multi-location breakpoints which was introduced by MI 3.
>>> +This has no effect when using MI version 3 or later.
>>
>> I needed to read this text and the one in NEWS several times before I
>> figured out what is meant here. How about this alternative instead:
>>
>> If your front end cannot yet migrate to a more recent version of the
>> MI protocol, you can nevertheless selectively enable specific features
>> available in those recent MI versions, using the following commands:
>>
>> @table @code
>>
>> @item -fix-multi-location-breakpoint-output
>> Use the output for multi-location breakpoints which was introduced by
>> MI 3, even when using MI versions 2 or 1. This command has no
>> effect when using MI version 3 or later.
>>
>> @end @table
>
> Thanks, I adopted this wording.
>
>> Otherwise, the documentation parts are OK.
>
> Thanks for the reviews.
>
> I am still open to comments about the code parts. In any case, the patch will
> remain up for review at least until the GDB 8.3 branch is created.
>
> Simon
>
>
This is now pushed.
Simon
next prev parent reply other threads:[~2019-03-13 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 19:57 Simon Marchi
2019-01-18 21:46 ` Eli Zaretskii
2019-01-21 17:09 ` Simon Marchi
2019-03-13 19:16 ` Simon Marchi [this message]
2019-05-10 10:42 ` --disable-gdbmi build broken Tom de Vries
2019-05-10 16:21 ` Simon Marchi
2019-05-10 17:01 ` Tom de Vries
2019-05-10 18:36 ` Simon Marchi
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=5c79a173-d2eb-3e84-5d73-d52b0ec5fe17@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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