From: Tom Tromey <tom@tromey.com>
To: Richard Bunt via Gdb-patches <gdb-patches@sourceware.org>
Cc: Richard Bunt <richard.bunt@linaro.org>,
Josh Cottingham <josh.cottingham@arm.com>
Subject: Re: [PATCH] gdb/mi: Fix printing of fortran strings in stack
Date: Wed, 10 May 2023 08:52:15 -0600 [thread overview]
Message-ID: <87ttwk5jds.fsf@tromey.com> (raw)
In-Reply-To: <20230510102031.2125810-1-richard.bunt@linaro.org> (Richard Bunt via Gdb-patches's message of "Wed, 10 May 2023 11:20:31 +0100")
>>>>> "Richard" == Richard Bunt via Gdb-patches <gdb-patches@sourceware.org> writes:
Richard> 547ce8f00b4ef826bdc9bf9a74f119fe9768852e fixed an issue where dynamic
Richard> types were not being resolved correctly prior to printing a value. The
Richard> same issue was discovered when printing the value using MI-mode. Solved
Richard> by porting the fix to the MI mode code path.
I wonder if this can be fixed more directly after
2fc3b8a4cb8439fc53975c4e70336d76e3ddc531 and its predecessors.
(Not that there's anything wrong with this patch.)
Tom
next prev parent reply other threads:[~2023-05-10 14:52 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 [this message]
2023-05-10 16:36 ` Richard Bunt
2023-05-12 18:38 ` Tom Tromey
2023-05-16 16:24 ` Richard Bunt
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=87ttwk5jds.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=josh.cottingham@arm.com \
--cc=richard.bunt@linaro.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).