SIGSEGV Error when debugging - suddenly appeared [solved]

[recobb]

I'm using 10.05 on a 64bit XP machine, doing simple (single file) console programs.  CB has been working great, including the debugger.  Something has changed, and I can't figure it out.  Now, almost every program I have written cannot be debugged.  Even trying to run to the first line of code results in:

Error while mapping shared library sections:
Program received signal SIGSEGV, Segmentation fault.
In ?? () (C:\WINDOWS\SysWOW64\guard32.dll)

Yet these programs (many unchanged) had no problems on this machine last week.  And I've been running them in the debugger on another machine (at the office) with identical hardware/software.  I can run them, inside of CB or outside, with no errors, so long as I don't try to debug them.  I have been able to open the 'hello world' main.c default project within the debugger, but nothing more complex (so, at least the debugger still seems to be there and linked to CB).

I have created new projects and then attached the code files to them, and I even reinstalled the Codeblocks Mingw package.  I've looked through the Settings and Project options and don't see anything there other than the default values that have been there all along.  I've also completely turned off my virus/firewall (Commodo), but no joy.

What happened?

Thanks,

Richard C

[xunxun]

That seemed like the problem of Comodo and the windows DEP. (http://forums.comodo.com/bug-reports/mingwgdb-error-5-t25287.0.html)
Could you try to disable windows DEP?

[oBFusCATed]

Can you try to debug you program with Gdb in a console?
Does that work?
If yes it is a C::B problem if not it is Gdb/System setup problem.

[recobb]

I guess this lets code::blocks off the hook:

(gdb) start
Breakpoint 1 at 0x403480:  line 814
Starting program: E:\Analysis\wxproj\shockspec/shockspecbatchops.exe
[New thread 4060.0x75c]
Error: dll starting at 0x77d40000 not found.
Error while mapping shared library sections:
NOT_AN_IMAGE: No such file or directory.
Error while mapping shared library sections:
C:\WINDOWS\SysWOW64\ntdll32.dll: No such file or directory.
Error: dll starting at 0x77d40000 not found.
Error: dll starting at 0x77c20000 not found.

Program received signal SIGSEGV, Segmentation fault.
0x100127d3 in ?? () from C:\WINDOWS\SysWOW64\guard32.dll

Now to go try a reboot with guard32.dll turned off in autoruns.

[recobb]

That seemed like the problem of Comodo and the windows DEP. (http://forums.comodo.com/bug-reports/mingwgdb-error-5-t25287.0.html)
Could you try to disable windows DEP?

Bingo.  I tried oBFusCATed's suggestion of running the debugger in the console - same error.  Then I disabled guard32.dll in autoruns, as suggested in the post you linked.  Still no joy.  So I combined that with Commodo's option to "Disable Defense+ Permanently (requires reboot)".  Then the debugger ran as normal.  Perhaps they updated more than the virus definitions in the past week.

Thanks to everyone for the help.  Time to talk to Commodo.

[recobb]

Found this on the Commodo forums:

http://forums.comodo.com/empty-t47299.0.html

I have found a way of making gdb run without disabling guard.dll.

You have to add gdb to the Image Execution Control exclusion list.

You do this Comodo->Defense+->Advanced->Image Execution Control Settings->Exclusions->Add->Browse...
Select gdb.exe and your problems are gone. GDB should now work perfectly...

I've tried it on a couple of programs, and so far, it seems to have fixed it.