This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Display Fortran strings in backtraces
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 29 Jul 2014 22:20:41 +0200
- Subject: Re: [patch] Display Fortran strings in backtraces
- Authentication-results: sourceware.org; auth=none
- References: <20140728214654 dot GA26290 at host2 dot jankratochvil dot net> <20140729200513 dot GA14672 at adacore dot 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