Eclipse Community Forums: C / C++ IDE (CDT)

Home » Language IDEs » C / C++ IDE (CDT) » gdb crash

Fri, 07 November 2008 18:13

Eclipse User

Originally posted by: noah.roberts.eng-software.com

I'm attempting to use gdb within eclipse on a project linked to wx dll.
Recently I downgraded to gdb 6.6 in order to get rid of it breaking in
ntdll land for no reason (google explained to do this). Now it crashes,
but only within eclipse!

If I run the program from msys, fine..works. If I run the program
within gdb from msys...works fine. If I run the program within gdb from
cmd (windows), it works just fine. If I run the program within gdb from
eclipse I get a SEGFAULT with a backtrace like this:

Thread [1] (Suspended: Signal 'SIGSEGV' received. Description:
Segmentation fault.)
4 <symbol is not available> 0x08458b00
3 __do_global_ctors() e:\wx2.8.9\include\wx-2.8\wx\list.h:511 0x004052bb
2 __mingw_CRTStartup() 0x0040122a
1 WinMainCRTStartup() 0x004012b8

I've tried many different configurations for the debugger settings and
so far nothing has had any effect.

Any ideas?

Re: gdb crash [message #226556 is a reply to message #226516]

Mon, 10 November 2008 03:20

Eclipse User

Noah Roberts wrote:

> Thread [1] (Suspended: Signal 'SIGSEGV' received. Description:
> Segmentation fault.)
> 4 <symbol is not available> 0x08458b00
> 3 __do_global_ctors() e:wx2.8.9includewx-2.8wxlist.h:511 0x004052bb
> 2 __mingw_CRTStartup() 0x0040122a
> 1 WinMainCRTStartup() 0x004012b8

> Any ideas?

I recall I'd seen some SIGSEGV in GDB (most likely it was GDB 6.3, but
issue was related to sockets). I was very surprized that program will run
after I resume it. Did you tried to resume?

Dmitry

Re: gdb crash [message #226874 is a reply to message #226556]

Mon, 17 November 2008 11:39

Eclipse User

Originally posted by: noah.roberts.eng-software.com

Dmitry Smirnov wrote:
> Noah Roberts wrote:
>
>> Thread [1] (Suspended: Signal 'SIGSEGV' received. Description:
>> Segmentation fault.)
>> 4 <symbol is not available> 0x08458b00
>> 3 __do_global_ctors() e:wx2.8.9includewx-2.8wxlist.h:511
>> 0x004052bb
>> 2 __mingw_CRTStartup() 0x0040122a
>> 1 WinMainCRTStartup() 0x004012b8
>
>> Any ideas?
>
> I recall I'd seen some SIGSEGV in GDB (most likely it was GDB 6.3, but
> issue was related to sockets). I was very surprized that program will
> run after I resume it. Did you tried to resume?
>
> Dmitry
>

Yep, terminated. I also tried rebooting, etc.

Re: gdb crash [message #226961 is a reply to message #226874]

Tue, 18 November 2008 07:21

Eclipse User

This seems to becoming my favorite question :-) but this is the only
method I know for problem localization.

Have you tried to debug the program with console gdb? Please do it from
clean windows command line and from MSYS console.

Debugging a program from console is simple:

> gdb MyProgram.exe
(gdb) run

Re: gdb crash [message #228578 is a reply to message #226961]

Fri, 09 January 2009 21:57

Eclipse User

Hello, I stumbled on this thread because I have a similar issue and I
followed your recommendation. When I use Eclipse/cdt/gdb I get the
following:

Thread [7] (Suspended: Signal 'SIGSEGV' received. Description:
Segmentation fault.)
5 <symbol is not available> 0x00330030
4 <symbol is not available> 0x07a1ffb4
3 ntdll!RtlSetInformationAcl() 0x7c927b7c
2 ntdll!RtlSetInformationAcl() 0x7c927ac9
1 <symbol is not available> 0x00000000

When I use gdb command line, I do not experience this problem. I am
working on an open source project in Qt and trying to debug a problem.
When a code calls open file dialog box, within a few seconds, this error
occurs and I can't get to the place I need to debug.

Working on:
Eclipse 3.4.1, CDT 5.0.1
MinGW-5.1.3, GNU gdb 6.6
Qt 4.3.1
Windows XP SP3

Any ideas???

Thanks,
Niraj

Re: gdb crash [message #228909 is a reply to message #228578]

Mon, 19 January 2009 01:23

Eclipse User

Niraj K Patel wrote:

> Any ideas???

Well, I do not know what to say.
Recently I also encountered similar issue: after some changes related to
threads/windows, my program has started to crash with SIGSEGV (when
debuggibg from CDT).
Command-line gdb does not report this exception, program is running
correctly. Program is not crashing if it is just running alone (i.e. not
attached to debugger).

I had found the workaround: if I set a breakpoint at the function that
causes a crash (in my case this is PeekMessage) and step over this
function, everything works fine. I even can disable this breakpoint after
first fit, nothing crashes...

Dmitry

Re: gdb crash [message #228947 is a reply to message #228909]

Mon, 19 January 2009 17:31

Eclipse User

Dmitry Smirnov wrote:

> I had found the workaround: if I set a breakpoint at the function that
> causes a crash (in my case this is PeekMessage) and step over this
> function, everything works fine. I even can disable this breakpoint after
> first fit, nothing crashes...

> Dmitry

Dmitry, I can't seem to get the stack information to tell me what's
causing the crash. I am linking it to debugged version of Qt library and
my code is has debug turned on, but it doesn't work. Looks like I'll have
to keep working with other alternatives. I am going to try Windows
version of DDD.

Niraj

Re: gdb crash [message #229070 is a reply to message #228947]

Tue, 20 January 2009 11:16

Eclipse User

Frontends like DDD (or Eclipse) are using GDB as a backend. I doubt you
will get any additional info. But it is more convinient for debug from UI
perspective, of course

Previous Topic:	Code completion, popup window & mouse pointer position
Next Topic:	Programmatically formatting C++ code

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 06:41:14 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter