Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Peter Jay Salzman <p@dirac.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb with intel fortran compiler
Date: Wed, 25 Feb 2004 20:26:00 -0000	[thread overview]
Message-ID: <20040225202622.GA22393@nevyn.them.org> (raw)
In-Reply-To: <20040225200653.GA13223@pete.localdomain>

On Wed, Feb 25, 2004 at 12:06:53PM -0800, Peter Jay Salzman wrote:
> I can't "list out of the box:
> 
>    p@satan$ gdb a.out 
>    (gdb) list
>    1       ../sysdeps/i386/elf/start.S: No such file or directory.
>            in ../sysdeps/i386/elf/start.S

This is typical.  It happens for a lot of non-Fortran programs also. 
start.S comes from glibc and is linked into every program.

> GDB doesn't like this expression in a conditional breakpoint:
> 
>    (gdb) break 11 if i == 12
>    A parse error in expression, near `= 12'.
> 
> but it does like this one:
> 
>    (gdb) break 11 if i = 12
>    Breakpoint 2 at 0x8049da9: file test.f90, line 11.

Are you sure it didn't modify the variable? :)

> Is this a GDB bug?  Is there a way to make expressions work the way they
> should work when debugging a F90 executable?

The only thing you're missing is that GDB does not support F90.  No
one's given serious time to the Fortran support in a few years now,
either.  So it's assuming that Fortran -> Fortran77, at a guess.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-25 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 20:12 Peter Jay Salzman
2004-02-25 20:26 ` Daniel Jacobowitz [this message]
2004-02-25 20:40   ` Peter Jay Salzman
2004-02-26  3:42     ` Daniel Jacobowitz

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=20040225202622.GA22393@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=p@dirac.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