--- Comment #8 from burnus at gcc dot gnu dot org 2007-12-09 22:48 ---
I believe this has been fixed by the patch (PR 22244):
http://gcc.gnu.org/ml/gcc-cvs/2007-12/msg00175.html
Note for gdb you still need the patches from:
http://sourceware.org/ml/gdb-patches/2007-11/msg00438.html
--- Comment #7 from burnus at gcc dot gnu dot org 2007-11-27 09:55 ---
I think this is fixed by the patch for PR 22244.
Patches:
http://gcc.gnu.org/ml/gcc-patches/2007-11/msg00888.html
http://gcc.gnu.org/ml/gcc-patches/2007-11/msg00903.html
--
http://gcc.gnu.org/bugzilla/show_bu
--- Comment #6 from pinskia at gcc dot gnu dot org 2005-10-28 12:04 ---
(In reply to comment #5)
> "set lang c" didn't give me that output. What is your configuration, gdb ,
> gfortran version and so on?
Oh, I did a "p array" since whatis is the same as ptype.
--
http://gcc.gnu.o
--- Comment #5 from woodzltc at sources dot redhat dot com 2005-10-28
04:42 ---
"set lang c" didn't give me that output. What is your configuration, gdb ,
gfortran version and so on?
My gdb session is like this:
(gdb) whatis array
type = Invalid type code (3) in symbol table.
(gdb)
--- Comment #4 from pinskia at gcc dot gnu dot org 2005-10-27 23:27 ---
This is more of a gdb bug as if I do:
set lang c
it prints out the array as a descriptor:
$2 = {data = 0x9a7f2d8, offset = -1, dtype = 265, dim = {{stride = 1, lbound =
1, ubound = 10}}}
--
http://gcc.gnu.org/bu
--- Additional Comments From woodzltc at sources dot redhat dot com
2005-06-30 08:48 ---
For array, ifc will output the following debuginfo:
<2><7e>: Abbrev Number: 4 (DW_TAG_variable) > TAG for variable "array"
DW_AT_decl_line : 2
DW_AT_decl_column : 42
DW_AT_d
