This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gdb 6.3 segfault at stack.c:294

From: Joost VandeVondele <jv244 at hermes dot cam dot ac dot uk>
To: Daniel Jacobowitz <drow at false dot org>
Cc: gdb at sources dot redhat dot com
Date: Mon, 6 Jun 2005 15:05:35 +0100 (BST)
Subject: Re: gdb 6.3 segfault at stack.c:294
References: <Pine.LNX.4.60.0506061428010.17046@hermes-1.csi.cam.ac.uk><20050606135852.GB27290@nevyn.them.org>

On Mon, Jun 06, 2005 at 02:44:05PM +0100, Joost VandeVondele wrote:

The executable is a fortran based one, compiled using NAG's f95
(which uses gcc to generate code AFAIK).


GDB is not tested using this compiler; if it generates its own debug
information, it's probably in some way incompatible with GDB.

This could possibly be, I have no idea how it is (mis?)using gcc ..

Presumably nsym is NULL. I can't imagine how that happened.

I think this is right :

(gdb) print nsym
$1 = (struct symbol *) 0x0

References:
- gdb 6.3 segfault at stack.c:294
  - From: Joost VandeVondele
- Re: gdb 6.3 segfault at stack.c:294
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]