This is the mail archive of the gdb@sourceware.org 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 crash

From: Mathew Yeates <mat dot yeates at gmail dot com>
To: Tom Tromey <tromey at redhat dot com>
Cc: gdb at sourceware dot org
Date: Tue, 10 Aug 2010 12:32:22 -0700
Subject: Re: gdb crash
References: <AANLkTi=-fqeWdY_=VePxGmDqdnah6ffWq1-Rsu4rqzg6@mail.gmail.com> <m3lj8eb76v.fsf@fleche.redhat.com>

yes. this is fortran on a 64 bit Linux machine.

On Tue, Aug 10, 2010 at 12:26 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Mathew" == Mathew Yeates <mat.yeates@gmail.com> writes:
>
> Mathew> with gdb-weekly-7.2.50.20100713 I frequently get the error
> Mathew> stack.c:293: internal-error: print_frame_args: Assertion `nsym != NULL' failed.
> Mathew> A problem internal to GDB has been detected,
> Mathew> further debugging may prove unreliable.
> Mathew> Quit this debugging session? (y or n) y
>
> Mathew> stack.c:293: internal-error: print_frame_args: Assertion `nsym != NULL' failed.
>
> Mathew> Is there anything I can do to help fix this?
>
> We need more information. ?What platform? ?What are you debugging?
> Do you have, or can you make, a simple test case?
>
> I know of this:
>
> ? ?http://sourceware.org/bugzilla/show_bug.cgi?id=11313
>
> However, I think this only happens with Fortran, or maybe also Pascal.
>
> Tom
>

References:
- gdb crash
  - From: Mathew Yeates
- Re: gdb crash
  - From: Tom Tromey

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