This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Problems while debugging fortran
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Carlos Eduardo Seo <cseo at linux dot vnet dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 24 Oct 2007 15:06:48 -0700
- Subject: Re: Problems while debugging fortran
- References: <46F2CE45.5020308@linux.vnet.ibm.com> <20070920204622.GB4368@adacore.com> <20070920205629.GA17779@caradoc.them.org> <46FAD136.5030406@linux.vnet.ibm.com> <20070926214619.GC9403@adacore.com> <471F70C0.3000206@linux.vnet.ibm.com> <20071024193336.GI11797@adacore.com> <20071024195719.GA16009@caradoc.them.org> <471FA810.6080506@linux.vnet.ibm.com> <471FBF9E.5000607@linux.vnet.ibm.com>
[moving to gdb-patches]
> 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?
> 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.
This is close to what I had in mind, but I would personally prefer
to limit this to Fortran compilation units. The semantics of this
attribute value are still a bit unclear, and I'd like us to be cautious
in its usage.
--
Joel