This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Testsuite: Fortran: 6.8 regression + gfortran updates
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 29 Dec 2008 07:48:45 +0400
- Subject: Re: [patch] Testsuite: Fortran: 6.8 regression + gfortran updates
- References: <20081208181523.GA23831@host0.dyn.jankratochvil.net>
> 2008-12-08 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.fortran/subarray.exp: Expect also the strings type output.
> * gdb.fortran/derived-type.exp: Likewise. Expect also the kind=X types.
> Update for the f-valprint.c modification from 2008-04-22.
Looks OK to me.
Just a few questions, out of curiosity.
> - "type = Type bar.*int4.*\:\: c.*real.*\:\: d.*End Type bar" \
> + "type = Type bar.*int.*\:\: c.*real.*\:\: d.*End Type bar" \
^^^^^^
What does the debugger print in your case? int8 or integer, or...?
> -gdb_test "print q%b" "\\$\[0-9\]+ = \\(.*a.*b.*c.*d.*e.*f.*g.*\\)"
> +gdb_test "print q%b" "\\$\[0-9\]+ = (\\(.*a.*b.*c.*d.*e.*f.*g.*\\)|'abcdefg')"
Under what circumstances will the debugger print the string as an array
of characters as opposed to a string?
--
Joel