From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Display Fortran strings in backtraces
Date: Tue, 29 Jul 2014 16:23:00 -0000 [thread overview]
Message-ID: <8738dkcgrg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20140728214654.GA26290@host2.jankratochvil.net> (Jan Kratochvil's message of "Mon, 28 Jul 2014 23:46:54 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> 2014-07-28 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * valprint.c (val_print_scalar_type_p): For TYPE_CODE_STRING return 0.
It looks fine to me, but I think it can affect Ada, so Joel ought to
weigh in.
Tom
next prev parent reply other threads:[~2014-07-29 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 3:54 Jan Kratochvil
2014-07-29 16:23 ` Tom Tromey [this message]
2014-07-29 20:20 ` Joel Brobecker
2014-07-29 20:27 ` Jan Kratochvil
2014-07-29 21:08 ` Joel Brobecker
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=8738dkcgrg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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