conflict with GDB debugger

I’m using the latest version cfp and CodeBlocks and the GCC compiler package, under windows OS
But when I debug my c++ program, I get segmentation fault. the error informatiion is:

Starting debugger:
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb
Child process PID: 2748
Program received signal SIGSEGV, Segmentation fault.
In ?? () (C:\WINDOWS\system32\guard32.dll)

and a MessageBox shows up saying “Program received signal SIGEGV , Segmentation fault. Do you want to view the backtrace?”

I clicked ok.

then I can see the call stack saying:
#0 10008961 ??() (C:\WINDOWS\system32\guard32.dll:??)
#1 00000000 ??() (??:??)

Is there anything wrong with the guard32.dll? Could you please check for it .

I confirm this problem. The same happens on my PC. The debugging process can be continued, but the crash message on every debugger run is annoying. Is there any workaround for this?

Steps to reproduce:

  1. Compile any application with mingw, with debugging info (-g switch).
  2. Run the application in GNU debugger (gdb app.exe, run, enter)
    The result:
    Program received signal SIGSEGV, Segmentation fault.
    0x10008961 in ?? () from C:\WINDOWS\system32\guard32.dll
    gdb.exe has all access rights granted.


As a temporarly workaround, you can disable guard32.dll from starting automatically (with the help of Sysinternals Autoruns, for example).
By my observations firewall and Defense+ work as expected without guard32.dll, but still i’m not sure because don’t know what guard32.dll is needed for by CFP.

[attachment deleted by admin]