From: Wu Zhou <woodzltc@cn.ibm.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: dinght@iopp.ccnu.edu.cn, fortran@gcc.gnu.org, bug-gdb@gnu.org,
gdb@sources.redhat.com
Subject: Re: Dose GDB support Fortran Cods?
Date: Mon, 08 Aug 2005 05:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0508081244110.30871@linux.site> (raw)
In-Reply-To: <3cba0545c8e7f2081629d88f12a85a9e@physics.uc.edu>
On Sun, 7 Aug 2005, Andrew Pinski wrote:
>
> On Aug 7, 2005, at 10:06 PM, Wu Zhou wrote:
>
> >
> > > command line,I use "gdb test",then I enter "list",but screen displays:
> > >
> > > 1 ../sysdeps/i386/elf/start.S: No such file or directory.
> > > in ../sysdeps/i386/elf/start.S
> >
> > This is a bug in GDB, we ever discussed a similar problem in:
> > http://sources.redhat.com/ml/gdb/2005-07/msg00228.html.
> >
> > BTW: there will be more chance you gdb/fortran problems get answered if
> > you ask in gdb@sources.redhat.com or fortran@gcc.gnu.org. It seems that
> > few people read bug-gdb@. :-)
>
> Actually it is really a bug in GCC for not emitting DW_AT_entry_point
> (dwarf-2) or N_MAIN (stabs), see PR 23280 which I just filed. (I thought
> there was already a bug filed but I could only find one for GCJ/java).
OK. I am not that sure about how gdb handle that. Daniel ever told me
that we can fix this in gdb's side by setting the main function to
"MAIN__" for Fortran programs.
It seems to me that emitting DW_AT_entry_point in gcc's side is a better
idea. But I am not sure whether gdb could handle it. When gcc do emit
DW_AT_entry_point, I will verify that. I had added myself into the
cc-list.
Regards
- Wu Zhou
prev parent reply other threads:[~2005-08-08 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 2:25 Wu Zhou
2005-08-08 2:40 ` Andrew Pinski
2005-08-08 5:29 ` Wu Zhou [this message]
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=Pine.LNX.4.63.0508081244110.30871@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=bug-gdb@gnu.org \
--cc=dinght@iopp.ccnu.edu.cn \
--cc=fortran@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=pinskia@physics.uc.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).