This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos Eduardo Seo wrote: > > > Daniel Jacobowitz wrote: >> Yes, this does seem sensible. > > Great, I can come up with a patch shortly. > > Regards, > Actually, I was re-reading this thread and I think we can use Wu Zhou's patch mentioned before. I've just refreshed it so it applies cleanly on CVS head and it's working fine with my Fortran binaries. What do you think? Any modifications suggested? Regards, - -- Carlos Eduardo Seo Software Engineer IBM Linux Technology Center -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHH7+eqvq7Aov/qQARAjNoAJ4hHCpEk9u1+gW/B5uVen+Rq0XWLwCeJ+9z KjKTK0t2acXQaM+HbLkT6/Y= =UjNN -----END PGP SIGNATURE-----
2007-10-24 Wu Zhou <woodzltc@cn.ibm.com> Carlos Eduardo Seo <cseo@linux.vnet.ibm.com> * dwarf2read.c (read_partial_die): check the value of DW_AT_calling_convention in Fortran programs. Index: src/gdb/dwarf2read.c =================================================================== --- src.orig/gdb/dwarf2read.c +++ src/gdb/dwarf2read.c @@ -5616,6 +5616,13 @@ read_partial_die (struct partial_die_inf case DW_AT_byte_size: part_die->has_byte_size = 1; break; + case DW_AT_calling_convention: + /* DWARF standard suggests to use value DW_CC_program of attribute + DW_AT_calling_convention to indicate the Fortran main program. + The following code is to check this. */ + if (DW_UNSND (&attr) == DW_CC_program) + set_main_name (part_die->name); + break; default: break; }
Attachment:
fortran-main.diff.sig
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |