From: Joost VandeVondele <jv244@hermes.cam.ac.uk>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.3 segfault at stack.c:294
Date: Mon, 06 Jun 2005 14:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.60.0506061503210.17046@hermes-1.csi.cam.ac.uk> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2005-06-06 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 13:44 Joost VandeVondele
2005-06-06 13:53 ` Vincent Rubiolo
2005-06-06 13:58 ` Joost VandeVondele
2005-06-06 13:59 ` Daniel Jacobowitz
2005-06-06 14:06 ` Joost VandeVondele [this message]
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.60.0506061503210.17046@hermes-1.csi.cam.ac.uk \
--to=jv244@hermes.cam.ac.uk \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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