public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: kamaraju@gmail.com
Cc: fortran@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: gfortran - gdb problem
Date: Mon, 25 Jul 2005 07:31:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.63.0507221735500.17445@wks190384wss.cn.ibm.com> (raw)

> $gdb ./a.out
> GNU gdb 6.3-debian
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain 
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
> 
> (gdb) l
> 1       ../sysdeps/i386/elf/start.S: No such file or directory.
>         in ../sysdeps/i386/elf/start.S
> (gdb)
> 
> 
> Normally, 'l' should display the source code. But it is giving some
> error. I am using debian sid, kernel 2.6.9-1-686. I tested the same
> thing with a helloworld program written in c and gdb works fine there.
>  
> 1) I am wondering whether it is a bug in either gdb or gfortran or
> packging of gfortran on Debian or some other thing?

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);

> 
> 2) Could anyone reproduce this?

I ever encountered similar problems on PPC platform.

Regards
- Wu Zhou

             reply	other threads:[~2005-07-25  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  7:31 Wu Zhou [this message]
2005-07-25 13:09 ` Daniel Jacobowitz
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=Pine.LNX.4.63.0507221735500.17445@wks190384wss.cn.ibm.com \
    --to=woodzltc@cn.ibm.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=kamaraju@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).