From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] gdb/fortran/testsuite: print values and types of string variables
Date: Wed, 16 Nov 2022 09:34:40 -0700 [thread overview]
Message-ID: <87o7t6uacf.fsf@tromey.com> (raw)
In-Reply-To: <df8d708ebf6b048f2c716ca444d9a0121220a2ab.1668185475.git.aburgess@redhat.com> (Andrew Burgess via Gdb-patches's message of "Fri, 11 Nov 2022 16:51:22 +0000")
>>>>> "Andrew" == Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> writes:
Andrew> While looking through the Fortran tests, I couldn't find a test of GDB
Andrew> printing the value and type of a Fortran string defined using the
Andrew> 'character*SIZE' notation.
Andrew> This works fine in GDB right now, but I thought it wouldn't hurt to
Andrew> have a test for this, so this commit adds such a test.
Seems good to me, though I don't actually know Fortran :)
Are there any tests of Fortran-style quoting of weird (control or
whatever) characters? If not, that might be a worthwhile addition.
Tom
next prev parent reply other threads:[~2022-11-16 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 16:51 Andrew Burgess
2022-11-16 16:34 ` Tom Tromey [this message]
2022-11-17 10:27 ` Andrew Burgess
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=87o7t6uacf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.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).