From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Display Fortran strings in backtraces
Date: Tue, 29 Jul 2014 20:27:00 -0000 [thread overview]
Message-ID: <20140729202041.GA20569@host2.jankratochvil.net> (raw)
In-Reply-To: <20140729200513.GA14672@adacore.com>
On Tue, 29 Jul 2014 22:05:13 +0200, Joel Brobecker wrote:
> Sorry, Jan. That seems to be counter-intuitive; strings are not
> scalars... The intent of the setting is to avoid having super-long
> parameter values drowning the list parameters. Strings can be pretty
> long, so I think the current behavior matches my current expectation.
In such case normal C 'char *' parameters also should not be printed.
Length of fortran strings is limited exactly the same way like C 'char *'
strings are:
Breakpoint 2, f (s='foo01010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010'..., _s=203) at ./gdb.fortran/fortran-frame-string.f90:24^M
(gdb) show print elements
Limit on string chars or array elements to print is 200.
What is the difference between Fortran strings and C 'char *' strings?
Thanks,
Jan
next prev parent reply other threads:[~2014-07-29 20:20 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
2014-07-29 20:20 ` Joel Brobecker
2014-07-29 20:27 ` Jan Kratochvil [this message]
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=20140729202041.GA20569@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.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