Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
I tried older version
GCC 9.5.0 + MinGW-w64 10.0.0 (MSVCRT) - release 1

But same bug.
2
I have spaces in my project directory.
3
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
4
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 ?? () ()
5
Plugins development / Re: GitBlock
« Last post by MoiCJarod on Today at 03:47:09 pm »
Hello !
I just managed to compile the plugin on an Ubuntu 22.04 (why only a Windows Release ?). I was able to copy the file on a fresh install of code::blocks on a virtual machine and it just worked. I swated blood to achieve this, so I want to share the obtained file :
http://gofile.me/3fqRi/zGalYdJZh
Cheers !
6
Nightly builds / Re: The 25 February 2024 build (13483) is out.
« Last post by Xaviou on Today at 12:24:42 pm »
Hi.

OS X version of this rev can be downloaded from my website.
There is only a macOS-11.6 version.
Note that it is not a notarized version of the application.

32 bits version for Windows can also be found in the same place.

Debian Bookworm and Bullseye (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04 and 23.10 versions can be installed from my ppa

Regards
Xav'
7
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.
8
Thanks!
9
Maybe I should install 64 bit 20.03 again, but add 32 bit mingw compiler to it? But I don't know how.
10
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/
Pages: [1] 2 3 4 5 6 ... 10