User forums > Using Code::Blocks

gcc debugger can not run

(1/3) > >>

codelighter:
I recently install the newest Mingw_w64 named x86_64-8.1.0-win32-sjlj-rt_v6-rev0 on my X64 Windows 10 OS, when I debug my C++ program, Code::Blocks throws me an error as below:
libgcc_s_seh-1.dll not found
the mingw thread model I select before install is win32,and excetpition model is sjlj not seh.

Anyone could help me out ? what's the right way to get things work? A detail introduction to seh,sjlj,posix,win32 options with Mingw_w64 would be appreciated. Thanks!

codelighter:
I have installed another version mingw_w64 x86_64-8.1.0-posix-seh-rt_v6-rev0, and this one make things work.
Now I want to know if mingw_w64 with SEH is the only support version for Code::Blocks? Anyone knows about it?

stahta01:
SEH, SJLJ, DWARF2 are most of the exception choices.

seh is the standard for Windows 64 bit. And, is not valid for 32 bit.
SJLJ is the most used of the standards for Windows 32 bit.

posix and win32 are threading choices.

Tim S.

codelighter:
Thanks very much! I have already tried  three different Mingw_W64 packages on my Win64 computer, and find out that only x86_64-8.1.0-win32-sjlj-rt_v6-rev0 can't debug normally.

codelighter:
Now I encounter another tricky problem with GDB debugger on my Win64 system.
The Debugger can not terminate normally. After I press the Stop Debugger Button, the debug output window will output similar lines like
Trying to interrupt process with pid: 5368; child pid: 5368 gdb pid: 13964, but the debugger is still in running, even if one minute later,
the Stop Debugger button is still in RED! Please refer to the attachment, you would find out the bizarre behaviour.

This is not the first time I encounter this phenomenon, actually I reinstall the Code::Blocks 17.12 for many times, the problem still exists.
It's very clumbsy to terminate the GDB debugger in the Task Manager Window or rebuild the project and only at this moment,
the Code::Blocks will force to  stop the GDB debugger.

I begin to doubt about if C::B doesn't support to work normally with GDB debugger on Win64, and CDB may be a better choice on my computer.

Anyone can explain the phenomenon?

Navigation

[0] Message Index

[#] Next page