public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Richard Bunt <richard.bunt@linaro.org>
To: Tom Tromey <tom@tromey.com>,
	Richard Bunt via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb/mi: Fix printing of fortran strings in stack
Date: Tue, 16 May 2023 17:24:57 +0100	[thread overview]
Message-ID: <30648a3b-221c-20ee-396a-727c5befcffc@linaro.org> (raw)
In-Reply-To: <87wn1d2y4m.fsf@tromey.com>



On 12/05/2023 19:38, Tom Tromey wrote:
>>>>>> "Richard" == Richard Bunt via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
>>> I wonder if this can be fixed more directly after
>>> 2fc3b8a4cb8439fc53975c4e70336d76e3ddc531 and its predecessors.
>>> (Not that there's anything wrong with this patch.)
>>> Tom
> 
> Richard> Even better than that, it fixes the issue I was seeing.
> 
> Nice.  I wonder if we can remove the old fix then.

I have confirmed that the fix applied to the cli-mode code path can be
removed.

I'll prepare a v2.

> 
> Richard> If it is OK, I'd like to propose the test case for upstream as I
> Richard> believe it covers a legitimate gap, even if there is no known bug
> Richard> here.
> 
> Yes, that would be great.  Thank you.
> 
> Tom

Thanks,

Rich.


      reply	other threads:[~2023-05-16 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 10:20 Richard Bunt
2023-05-10 13:13 ` Andrew Burgess
2023-05-10 14:52 ` Tom Tromey
2023-05-10 16:36   ` Richard Bunt
2023-05-12 18:38     ` Tom Tromey
2023-05-16 16:24       ` Richard Bunt [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=30648a3b-221c-20ee-396a-727c5befcffc@linaro.org \
    --to=richard.bunt@linaro.org \
    --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).