public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: Tom Tromey <tom@tromey.com>,
	Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb/mi: add no-history stop reason
Date: Fri, 6 Jan 2023 10:52:29 +0100	[thread overview]
Message-ID: <983476e8-1226-11a2-c982-d03efb2f40a7@redhat.com> (raw)
In-Reply-To: <87o7rcda5m.fsf@tromey.com>

On 05/01/2023 21:00, Tom Tromey wrote:
>>>>>> Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
>> This problem was reported as record/29260.
>> This commit adds the reason no-history to the record, making it easier
>> for interfaces using the mi interpreter to report the result.  It also
>> changes the test gdb.mi/mi-reverse.exp to test that the reason shows up
>> correctly.
> Thank you.  This is ok.

Thanks!

pushed

> Tom
>

-- 
Cheers,
Bruno


      reply	other threads:[~2023-01-06  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 14:54 Bruno Larsen
2023-01-05 20:00 ` Tom Tromey
2023-01-06  9:52   ` Bruno Larsen [this message]

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=983476e8-1226-11a2-c982-d03efb2f40a7@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).