This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb with intel fortran compiler
- From: Daniel Jacobowitz <drow at false dot org>
- To: Peter Jay Salzman <p at dirac dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 25 Feb 2004 15:26:22 -0500
- Subject: Re: gdb with intel fortran compiler
- References: <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