Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: kamaraju@gmail.com, fortran@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: gfortran - gdb problem
Date: Mon, 25 Jul 2005 13:09:00 -0000	[thread overview]
Message-ID: <20050725130929.GA2090@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0507221735500.17445@wks190384wss.cn.ibm.com>

On Fri, Jul 22, 2005 at 05:43:51PM +0800, Wu Zhou wrote:
> > (gdb) l
> > 1       ../sysdeps/i386/elf/start.S: No such file or directory.
> >         in ../sysdeps/i386/elf/start.S

This happens if you have debugging information for start.S, but not for
main.

> Maybe it is a packaging problem.  On my Fedora Core 4, it shows the 
> following text:
> 
> (gdb) l
> 5          We call it from the main() function in this file.  */
> 6       void MAIN__ (void);
> 7
> 8       /* Main procedure for fortran programs.  All we do is set up the environment
> 9          for the Fortran program.  */
> 10      int
> 11      main (int argc, char *argv[])
> 12      {
> 13        /* Set up the runtime environment.  */
> 14        set_args (argc, argv);

This happens if you have debugging information for libfortran.

Really, GDB ought to know that the main function in a Fortran program
is named MAIN__ and set that to the default location.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-07-25 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  7:31 Wu Zhou
2005-07-25 13:09 ` Daniel Jacobowitz [this message]
2005-07-26  3:05   ` Wu Zhou
2005-07-26  3:19     ` Daniel Jacobowitz
2005-07-26  6:57       ` David Lecomber
2005-07-26  9:01       ` Wu Zhou
2005-07-26 13:06         ` Daniel Jacobowitz
2005-07-28  3:43           ` Wu Zhou

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=20050725130929.GA2090@nevyn.them.org \
    --to=drow@false.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=kamaraju@gmail.com \
    --cc=woodzltc@cn.ibm.com \
    /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