From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: Re: Problems while debugging fortran
Date: Thu, 25 Oct 2007 20:32:00 -0000 [thread overview]
Message-ID: <4720F17E.6000508@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071025193515.GA3729@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Jacobowitz wrote:
> On Thu, Oct 25, 2007 at 12:30:41PM -0700, Jim Blandy wrote:
>> This would be fine with me, too.
>
> Me too.
>
Ok. I added Joel's comments to the patch, replacing the original ones.
If no one has any other objections, I can commit this later.
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
iD8DBQFHIPF+qvq7Aov/qQARAjcnAJ0SBFHaOnQrkzN2C0hsKuuYr5bhLQCeJLMS
OI9Fa1ZuhUQ7/h9lV19q86w=
=+biI
-----END PGP SIGNATURE-----
[-- Attachment #2: fortran-main.diff --]
[-- Type: text/x-patch, Size: 1282 bytes --]
2007-10-25 Wu Zhou <woodzltc@cn.ibm.com>
Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Joel Brobecker <brobecker@adacore.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,19 @@ read_partial_die (struct partial_die_inf
case DW_AT_byte_size:
part_die->has_byte_size = 1;
break;
+ case DW_AT_calling_convention:
+ /* In Fortran programs compiled with XLF, the only way we have found
+ so far to identify the main procedure is by using the fact that
+ the calling convention is different from the other procedures:
+ The DW_AT_calling_convention attribute is set to DW_CC_program.
+
+ This is not the intent of this attribute as documented in the
+ DWARF standard, but we haven't found any other distinctive
+ characteristic of the main procedure, so we check the calling
+ convention for Fortran compilation units. */
+ if ((DW_UNSND (&attr) == DW_CC_program) && (cu->language == language_fortran))
+ set_main_name (part_die->name);
+ break;
default:
break;
}
[-- Attachment #3: fortran-main.diff.sig --]
[-- Type: application/octet-stream, Size: 65 bytes --]
next prev parent reply other threads:[~2007-10-25 20:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46F2CE45.5020308@linux.vnet.ibm.com>
[not found] ` <20070920204622.GB4368@adacore.com>
[not found] ` <20070920205629.GA17779@caradoc.them.org>
[not found] ` <46FAD136.5030406@linux.vnet.ibm.com>
[not found] ` <20070926214619.GC9403@adacore.com>
[not found] ` <471F70C0.3000206@linux.vnet.ibm.com>
[not found] ` <20071024193336.GI11797@adacore.com>
[not found] ` <20071024195719.GA16009@caradoc.them.org>
[not found] ` <471FA810.6080506@linux.vnet.ibm.com>
[not found] ` <471FBF9E.5000607@linux.vnet.ibm.com>
2007-10-24 22:14 ` Joel Brobecker
2007-10-25 14:10 ` Carlos Eduardo Seo
2007-10-25 15:41 ` Jim Blandy
2007-10-25 16:15 ` Daniel Jacobowitz
2007-10-25 16:18 ` Carlos Eduardo Seo
2007-10-25 17:05 ` Jim Blandy
2007-10-25 18:19 ` Daniel Jacobowitz
2007-10-25 19:05 ` Jim Blandy
2007-10-25 19:23 ` Joel Brobecker
2007-10-25 19:10 ` Joel Brobecker
2007-10-25 19:35 ` Jim Blandy
2007-10-25 20:00 ` Daniel Jacobowitz
2007-10-25 20:32 ` Carlos Eduardo Seo [this message]
[not found] <19c433eb0710250906k392cecf8t1f99595d5c5a8107@mail.gmail.com>
[not found] ` <20071025170621.GA27275@caradoc.them.org>
[not found] ` <m3lk9rxceq.fsf@codesourcery.com>
[not found] ` <20071025190150.GA1560@caradoc.them.org>
[not found] ` <m3tzof9eqq.fsf@codesourcery.com>
[not found] ` <20071025202406.GC4063@adacore.com>
2007-10-25 20:41 ` Carlos Eduardo Seo
2007-10-25 20:55 ` Joel Brobecker
2007-10-25 21:47 ` Carlos Eduardo Seo
2007-10-25 20:57 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4720F17E.6000508@linux.vnet.ibm.com \
--to=cseo@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox