[Bug fortran/17905] allocated arrays not visible with gdb

[Bug fortran/17905] allocated arrays not visible with gdb

[pinskia at gcc dot gnu dot org]

------- 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/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[woodzltc at sources dot redhat dot com]

------- 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) set language c
Warning: the current language does not match this frame.
(gdb) whatis array
type = struct array1_int4
(gdb)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[pinskia at gcc dot gnu dot org]

------- 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.org/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[burnus at gcc dot gnu dot org]

------- 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_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[burnus at gcc dot gnu dot org]

------- 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

Result with current gfortran and Intel's idb 10.1:

(idb) b test.f90:3
Breakpoint 1 at 0x4008fe: file test.f90, line 3.
(idb) run
INTERNAL ERROR: unexpected address for .text of /dev/shm/a.out
Expected = 0x0000000000600000, actual = 0x0000000000400000, diff =
0xffffffffffe00000
Starting program: /dev/shm/a.out

Breakpoint 1, test () at test.f90:3
3             allocate (array(10))
(idb) next
4             array = 3
(idb) next
5             array(1) = 4
(idb) ptype array
type = INTEGER(4)(10)
(idb) p array
$1 = {3, 3, 3, 3, 3, 3, 3, 3, 3, 3}


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[woodzltc at sources dot redhat dot com]

------- 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_decl_file   : 1
     DW_AT_accessibility: 1     (public)
     DW_AT_name        : array
     DW_AT_type        : <99>    ====> next TAG, indicating that it is an array
     DW_AT_location    : 5 byte block: 3 50 23 9 8      (DW_OP_addr: 8092350)
     DW_AT_external    : 0
     DW_AT_start_scope : 26

 <1><99>: Abbrev Number: 5 (DW_TAG_array_type)
     DW_AT_ordering    : 1      (column major)
     DW_AT_type        : <cb>
     DW_AT_data_location: 2 byte block: 97 6    (DW_OP_push_object_address;
DW_OP_deref)
     DW_AT_allocated   : 11 byte block: 97 10 c 22 6 c 1 0 0 0 1a      
(DW_OP_push_object_address; DW_OP_constu: 12; DW_OP_plus; DW_OP_deref;
DW_OP_const4u: 1; DW_OP_and)

If gfortran could output similar debuginfo, gdb could handle it correctly. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |woodzltc at sources dot
                   |                            |redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-10-09 16:32 -------
I saw something like this too.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-debug


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17905

[Bug fortran/17905] allocated arrays not visible with gdb

[tobi at gcc dot gnu dot org]

------- Additional Comments From tobi at gcc dot gnu dot org  2004-10-09 14:00 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-10-09 14:00:39
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17905