I use Code::Blocks 20.03 64bit with w64devkit toolchain. Every time I try to debug my program - Iconv.exe crash is reported before launching it. Everything else works as usual, i.e. debugging itself works properly. For what reason Iconv.exe is launched? Is it launched by Code::Blocks or GDB? Can I fix this problem somehow? It's annoying.
You did not specify which OS you are running code::blocks on.
Maybe this will partially help with the search.https://en.wikipedia.org/wiki/Iconv
OS is Windows. Error is BEX according to crash report. So it's caused by attempt to execute data. Crash can possibly be fixed via adding Iconv.exe to DEP white list, but I don't think it's good idea. As Iconv.exe doesn't affect anything, then may be there is some way to disable it? Is it executed by Code::Blocks?
To help you, we have to guess which Windows it is?
- Windows 3.1
- Windows 95
- Windows 98
- Windows XP 32 bit or 64bit
- Windows XP 32 bit or 64bit with SP1 SP2 SP3
- Windows NT 32 bit or 64bit
- Oh, I forgot about: Windows Me Millennium :)
- Windows Vista 32 bit or 64bit
- Windows 7 32 bit or 64bit
- Windows 7 32 bit or 64bit with SP1
- Windows 8 32 bit or 64bit
- Windows 10 32 bit or 64bit
- Windows 11 32 bit or 64bit
- Windows Sever ...
The more information you provide, the easier it will be to understand what the problem is.Also, in some cases, you need to attach a screenshot or a link to a video or animation to the post.You can also specify the link from where you downloaded the code blocks.
Attached a screenshot as an example.
Quote from: Mr.Madguy on November 17, 2023, 10:23:01 PM
OS is Windows. Error is BEX according to crash report. So it's caused by attempt to execute data. Crash can possibly be fixed via adding Iconv.exe to DEP white list, but I don't think it's good idea. As Iconv.exe doesn't affect anything, then may be there is some way to disable it? Is it executed by Code::Blocks?
On my Computer (Win 10 64 bit) "Iconv.exe" is not part of an nightly CB build; but, it is part of an MinGW GCC toolchain. So, you should ask the people who built the MinGW toolchain you are using.
Edit: Web searching implied gdb.exe called "Iconv.exe" and the posters implied it might be a bug in gdb.
Tim S.