This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb 6.3 segfault at stack.c:294
- From: Daniel Jacobowitz <drow at false dot org>
- To: Joost VandeVondele <jv244 at hermes dot cam dot ac dot uk>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 6 Jun 2005 09:58:52 -0400
- Subject: Re: gdb 6.3 segfault at stack.c:294
- References: <Pine.LNX.4.60.0506061428010.17046@hermes-1.csi.cam.ac.uk>
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.
> Program received signal SIGSEGV, Segmentation fault.
> print_frame_args (func=Variable "func" is not available.
> ) at stack.c:294
> 294 if (SYMBOL_CLASS (nsym) == LOC_REGISTER)
> (gdb) list
> 289 {
> 290 struct symbol *nsym;
> 291 nsym = lookup_symbol
> 292 (DEPRECATED_SYMBOL_NAME (sym),
> 293 b, VAR_DOMAIN, (int *) NULL, (struct symtab **)
> NULL);
> 294 if (SYMBOL_CLASS (nsym) == LOC_REGISTER)
> 295 {
> 296 /* There is a LOC_ARG/LOC_REGISTER pair. This
> means that
> 297 it was passed on the stack and loaded into a
> register,
> 298 or passed in a register and stored in a stack
> slot.
Presumably nsym is NULL. I can't imagine how that happened.
--
Daniel Jacobowitz
CodeSourcery, LLC