User forums > Help

Can't debug - GDB segfaults

(1/2) > >>

mmebane:
I'm using the latest SVN build on Windows XP, with MinGW 5.0.3 installer and latest MinGW candidates.

Anyway, every time I try to debug something, GDB crashes on me with a segfault, before I have a chance to do anything.

Code::Blocks is built with GCC 4.1.1, if that matters. I haven't tried rebuilding it with 3.4.5.
It doesn't seem to matter whether I compile my projects with 4.1.1 or 3.4.5.


--- Code: ---Building to ensure sources are up-to-date
Build succeeded
Selecting target: Debug|Win32
Adding source dir: C:\Documents and Settings\Mitchell\My Documents\Baylor\2006-02 - Fall\CSI 3334-01\src\Project 2 - Shortest-path maze solver\Project 2 - Shortest-path maze solver\
Adding source dir: C:\Documents and Settings\Mitchell\My Documents\Baylor\2006-02 - Fall\CSI 3334-01\src\Project 2 - Shortest-path maze solver\Project 2 - Shortest-path maze solver\
Adding file: Project 2 - Shortest-path maze solver.exe
Starting debugger: done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 6.3
Program received signal SIGSEGV, Segmentation fault.
In ntdll!RtlpWaitForCriticalSection () (ntdll.dll)

--- End code ---

I couldn't find any other references to this on the forum, so is it just me?

crzysdrs:
I haven't seen quite the same issue but I am using C::B under Gentoo Linux (the latest Subversion) and my debugger doesn't seem to work "as advertised". I see no indicator of what line I am on and all I can really do with the debugging is to just run it. The only clues the debugger gives me is when the application segfaults and gives me a backtrace. Breakpoints don't seem to work nor does trying to step through the code. Perhaps our two issues are intertwined (as we are both using subversion builds)?

mmebane:
This is interesting... I just noticed that debugging still does work, even after the segfault. I wonder what is segfaulting?

Ceniza:
It seems it's your program the one that is segfaulting. Have you tried to run it from a console? Do you get the segfault that way? Is there anything useful from the backtrace?

mmebane:
It's not me - even the CodeBlocks sample C++ Hello World program segfaults if I try to debug it.

Oh, and the backtrace is not helpful - almost entirely unknown symbols. :/

Weird.

Navigation

[0] Message Index

[#] Next page