--- Comment #5 from burnus at gcc dot gnu dot org 2009-05-29 07:43 ---
Is this a duplicate of PR 40040?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24526
--- Comment #4 from burnus at gcc dot gnu dot org 2008-08-21 21:31 ---
I think the gfortran part is fixed by PR 29635. The rest has to be solved in
gdb. Other debugers seem to have also some problems, e.g. Intel's idb, cf.
http://gcc.gnu.org/ml/fortran/2008-08/msg00128.html
--
http:
--- Comment #3 from steven at gcc dot gnu dot org 2006-10-14 14:21 ---
There is support for Fortran module variables in DWARF3, see
http://dwarf.freestandards.org/Dwarf3.pdf.
Unfortunately GDB doesn't seem to support this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24526
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-10-27 23:15 ---
(In reply to comment #1)
> To let gdb recognize 'a' directly, some trick in gdb might be needed.
I don't know if some trickery is needed, just we might need to emit something
like what C++ does with it using stateme
--- Comment #1 from woodzltc at sources dot redhat dot com 2005-10-26
03:25 ---
Variable a in modular foo is represented as __foo__a in the DWARF output. So
you can use "print __foo__a" to get the value of modular variable a.
[EMAIL PROTECTED] ~]$ gdb -q ./modular
Using host libthread
