From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: Problems while debugging fortran
Date: Wed, 24 Oct 2007 16:20:00 -0000 [thread overview]
Message-ID: <471F70C0.3000206@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070926214619.GC9403@adacore.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joel Brobecker wrote:
>
> Unfortunately, this is an idea that has already been discussed a
> couple of years ago, and people felt that this was not the intent
> of that attribute. See:
>
> http://www.cygwin.com/ml/gdb-patches/2005-11/msg00380.html
>
> I haven't followed any development on the DWARF3 side whether
> something more appropriate has been introduced for that purpose.
>
> What compiler are you using? Do you have any control on what your
> compiler does? Perhaps you can add an extra symbol like we do with
> the Ada compiler? Just some thoughts...
The compiler is XLF and the only way it tags the "main" function is by
adding DW_AT_calling_convention = DW_CC_program. Unfortunately, I
don't have any control over the compiler, so I'm stuck with this. Any
other thoughts?
Thanks and 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
iD8DBQFHH3C/qvq7Aov/qQARAldZAJ4kQSm43hBsKggHPurQ6HLAjbwN6gCeP+lX
VpHrh1Pt3tETq78AWNFoPZc=
=9/uV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-24 16:20 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 [this message]
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
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=471F70C0.3000206@linux.vnet.ibm.com \
--to=cseo@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.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