From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>,
drow@sourceware.org, gdb@sourceware.org
Subject: Re: Problems while debugging fortran
Date: Wed, 24 Oct 2007 21:56:00 -0000 [thread overview]
Message-ID: <471FBF9E.5000607@linux.vnet.ibm.com> (raw)
In-Reply-To: <471FA810.6080506@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
-----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-----
[-- Attachment #2: fortran-main.diff --]
[-- Type: text/x-patch, Size: 838 bytes --]
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 #3: fortran-main.diff.sig --]
[-- Type: application/octet-stream, Size: 65 bytes --]
next prev parent reply other threads:[~2007-10-24 21:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 11:37 Carlos Eduardo Seo
2007-09-20 19:47 ` Joel Brobecker
2007-09-20 20:46 ` Carlos Eduardo Seo
2007-09-20 20:56 ` Joel Brobecker
2007-09-21 6:52 ` Daniel Jacobowitz
2007-09-26 21:46 ` Carlos Eduardo Seo
2007-09-26 21:51 ` Joel Brobecker
2007-10-24 16:20 ` Carlos Eduardo Seo
2007-10-24 19:33 ` Joel Brobecker
2007-10-24 19:57 ` Daniel Jacobowitz
2007-10-24 20:16 ` Carlos Eduardo Seo
2007-10-24 21:56 ` Carlos Eduardo Seo [this message]
2007-09-26 21:51 ` Pierre Muller
2007-09-23 2:52 ` Carlos Eduardo Seo
2007-09-24 10:01 ` Joel Brobecker
2007-09-24 23:49 ` Carlos Eduardo Seo
2007-09-25 1:29 ` Joel Brobecker
2007-09-25 17:34 ` Carlos Eduardo Seo
2007-09-26 6:29 ` Joel Brobecker
2007-10-25 16:07 François-Xavier Coudert
2007-10-25 17:06 ` Daniel Jacobowitz
2007-10-25 18:44 ` Jim Blandy
2007-10-25 19:01 ` Daniel Jacobowitz
2007-10-25 19:27 ` Jim Blandy
2007-10-25 20:24 ` Joel Brobecker
2007-10-25 20:36 ` Carlos Eduardo Seo
2007-10-25 20:41 ` Joel Brobecker
2007-10-25 20:55 ` 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=471FBF9E.5000607@linux.vnet.ibm.com \
--to=cseo@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@sourceware.org \
--cc=gdb@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