Author Topic: Codeblocks 32 bit 20.03 with mingw is broken. Doesn't find compiler and debugger  (Read 6264 times)

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I installed 64 bit code blocks 20.03 with mingw. I tried to compile 32 bit application with -m32 flag but it doesn't work because there are no 32 bit libraries.
https://forums.codeblocks.org/index.php?topic=23868.0

Because of that I downloaded 32 bit code blocks 20.03 with mingw. After installation and running it, it showed error that there is no compiler executable. I had to fix path to compiler and file names. After that it worked and I compiled my 32 bit application.
When I run my application it crashes at some point. I wanted to find out why so I compiled debug version with debugging symbols and I run it with debugger. However, when the application crashes the debugger doesn't show line of code that makes it crash, debugger is broken.

Then I installed codeblocks 17.02 32 bit. When I try to debug there is error that debugger cannot be found. After I set it to C:\Program Files (x86)\CodeBlocks\MinGW\bin\gdb32.exe when I try to debug, I get "Debugger finished with status 1" when trying to debug my application.

What to do now when no codeblocks version works? I will look for alternatives.
https://alternativeto.net/software/codeblocks/

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
Maybe I should install 64 bit 20.03 again, but add 32 bit mingw compiler to it? But I don't know how.

Offline Grit Clef

  • Multiple posting newcomer
  • *
  • Posts: 67
  • Where there is a will, there is a way.
Simply Install CodeBlocks 64 bit, and download a 32 bit gcc, you can get it run. Some sources that you can download gcc-on-Windows packages from can be such as https://www.winlibs.com/, then set it in your 64 bit CodeBlocks compiler Settings.
-Windows 7, 32-bit
-CodeBlocks r13518, gcc 13.2.0, debug version

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
Simply Install CodeBlocks 64 bit, and download a 32 bit gcc, you can get it run. Some sources that you can download gcc-on-Windows packages from can be such as https://www.winlibs.com/, then set it in your 64 bit CodeBlocks compiler Settings.

I installed codeblocks 20.03 64-bit.
I downloaded this:
GCC 13.2.0 (with POSIX threads) + LLVM/Clang/LLD/LLDB 17.0.6 + MinGW-w64 11.0.1 (MSVCRT) - release 5   (LATEST)

Unpacked it and set in Codeblocks to use this compiler.
I also set debugger to this GCC 13.2.0 that I downloaded.

When I compile my program it compiles. I rebuild it. When I try to debug it, the debugger doesn't work because it doesn't show line of code where my application crashes. I compiled debug version with debugging symbols. But debugger doesn't work.
Also when I click "Break debugger" before my application crashes, nothing happens.

Quote
Trying to interrupt process with pid: 3216; child pid: 3216 gdb pid: 10872
In ?? () ()

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
Quote
[debug]Thread 25 received signal SIGSEGV, Segmentation fault.
[debug][Switching to Thread 7332.0x2b84]
[debug]0x011df854 in ?? ()
[debug]>>>>>>cb_gdb:

In ?? () ()

[debug]> bt 30
[debug]#0  0x011df854 in ?? ()
[debug]Backtrace stopped: Cannot access memory at address 0x443ec004
[debug]>>>>>>cb_gdb:

Debugger finished with status 0

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I have spaces in my project directory.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I tried older version
GCC 9.5.0 + MinGW-w64 10.0.0 (MSVCRT) - release 1

But same bug.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I installed codeblocks competition called CodeLite. But it's even worse than codeblocks, it doesn't compile when there are spaces in path.
https://github.com/eranif/codelite/issues/1845

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I tried GCC 7.5.0 + MinGW-w64 7.0.0 (MSVCRT) - release 1

Debugger doesn't work.

Offline sodev

  • Regular
  • ***
  • Posts: 498
I don't know why you think you can solve your problem by downgrading even further. Especially for such a well known, longstanding problem, like spaces in paths.

But you already named the issue, spaces in path, and there is a simple solution for this: remove the spaces.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I don't know why you think you can solve your problem by downgrading even further. Especially for such a well known, longstanding problem, like spaces in paths.

But you already named the issue, spaces in path, and there is a simple solution for this: remove the spaces.

It's not because of spaces. I copied the project to path without spaces, opened it and started debugger. Same problem. Debugger runs but doesn't work correctly, doesn't display line of code.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
I have 64 bit operating system, 64 bit codeblocks, 32 bit MINGW. If that matters. I tried both 32 bit GDB and 64 bit. Same result.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
When I debug my application, when I set breakpoints they work. But when my application crashes it doesn't show on what line of code.

Offline hidrerarta

  • Multiple posting newcomer
  • *
  • Posts: 12
My application crashes when there is a lot of graphics data displayed with opengl. When I stop displaying text it doesn't crash. But debugger doesn't show any information where it crashes.

Offline sodev

  • Regular
  • ***
  • Posts: 498
I am not an expert of GDB but if the crash does happen inside an external library you need the debugging symbols of that library as well. But even without you should get a backtrace of at least the path inside your application.