gdb crash

gdb crash

[Mathew Yeates]

with gdb-weekly-7.2.50.20100713 I frequently get the error
stack.c:293: internal-error: print_frame_args: Assertion `nsym != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

stack.c:293: internal-error: print_frame_args: Assertion `nsym != NULL' failed.

Is there anything I can do to help fix this?

-Mathew

Re: gdb crash

[Tom Tromey]

>>>>> "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

Re: gdb crash

[Mathew Yeates]

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
>

gdb crash

[Łukasz Michalski]

Hi,

I am developing application using wxWindows for Linux and MS Windows
platforms using wxWindows. Under windows I am using mingw with latest
patches and Dev-Cpp (latest beta)

I have problems using gdb under windows. When I run my application
standalone everything works correct. But when run under gdb app crashes and
gdb crashes just after.

When I try to run app step-by-step by setting breakpoint to first line and
stepping over gdb crashes when accessing first static variable.

It crashes always with the same message:
Access violation in gdb exe. Memory at address 0x0000004 cannot be "read".

I want to generate reasonable bug report, but I have no idea how to do it.
My app with debug info has 45Mb and is linked with wxWindows compiled
with -g flag and some other smaller libraries also compiled with -g flag.

Here are versions of compiler and gdb:
C:\>gdb -v
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
[...]
This GDB was configured as "mingw32".

C:\>gcc -v
Reading specs from P:/DevCpp/bin/../lib/gcc-lib/mingw32/3.2/specs
Configured with:
../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=
mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --en
able
-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared
Thread model: win32
gcc version 3.2 (mingw special 20020817-1)

I can try to strip the code, but cannot make my app independent of wxWindows
and I use slightly modified version than original.

I will be very graceful for any suggestions what to do to make gdb work.

Under Linux everything works fine.

Regards,
ÂŁukasz Michalski