Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
21
Development / Re: Small patch for out of bounds warning.
« Last post by grem on March 14, 2024, 11:31:44 pm »
Applied in https://sourceforge.net/p/codeblocks/code/13491/

Thanks to Miguel Gimenez.
22
Please try to create Project via project wizard initially (menu "File - New - Project") and then add file or files to compile into project. Then try to rebuild it.
23
Using Code::Blocks / Re: Debugger - Memory dump
« Last post by Pecan on March 14, 2024, 09:30:40 pm »
Sorry, but I'm using Linux Mint.

My error. You do not need the -d startup option.
You can still copy any item in the debuggers log.

See below using Linux Mint.
24
Using Code::Blocks / Configuring project compilation (example Dislin library)
« Last post by tuchin on March 14, 2024, 08:56:46 pm »
After the project settings, the compilation lines look like:
Code
g++.exe -Wall -m64 -fexceptions -std=c++20 -g -Wall  -c N:\MyProgramming\Dislin\exa_cpp.cpp -o obj\Debug\exa_cpp.o
g++.exe  -o bin\Debug\Dislin.exe obj\Debug\exa_cpp.o  -m64 -lopengl32  N:\MyProgramming\Dislin\discpp.a
I need to rearrange in a row -lopengl32 and N:\MyProgramming\Dislin\discpp.a:
Code
N:\MyProgramming\Dislin\discpp.a -lopengl32

Can you tell me how to do this? The project https://disk.yandex.ru/d/kc0-onWyk-Tr5g
25
Using Code::Blocks / Re: Debugger - Memory dump
« Last post by Evan on March 14, 2024, 08:50:26 pm »
Sorry, but I'm using Linux Mint.
26
Using Code::Blocks / Re: Debugger - Memory dump
« Last post by Pecan on March 14, 2024, 08:43:15 pm »
@evan

No, I mean the "CodeBlocks.exe -d "  option flag.
Or /d for windows. Run "codeblocks /?" for into.

My error. The debuggers log is there wether the -d options is used or not.
27
Using Code::Blocks / Re: Debugger - Memory dump
« Last post by Evan on March 14, 2024, 07:40:22 pm »
I assume you mean the -d option can be set as an argument in debugger default settings. If so, I can't see any address.

My debugger log:

Active debugger config: GDB/CDB debugger:Default
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: /home/evan/Desktop/C/DB/
Adding source dir: /home/evan/Desktop/C/DB/
Adding file: /home/evan/Desktop/C/DB/bin/Debug/DB
Changing directory to: /home/evan/Desktop/C/DB/.
Set variable: LD_LIBRARY_PATH=.:
Starting debugger: /usr/bin/gdb -nx -fullname -quiet -d -args /home/evan/Desktop/C/DB/bin/Debug/DB
Setting SHELL to '/bin/sh'
done
Setting breakpoints
Debugger name and version: GNU gdb (Debian 13.1-3) 13.1
Child process PID: 103102
28
Using Code::Blocks / Re: Debugger - Memory dump
« Last post by Pecan on March 14, 2024, 03:59:30 pm »
See if this works.
Try running CodeBlocks with the -d option to show the debuggers log. You can copy from the log by marking the address, right clicking, and selecting "copy selection".
29
Use the built-in Resource Monitor, see the second answer in this post for a guide.
30
The "No project/No target/Unknown compiler" message has no sense, and

That means the OP is not using an CB project.

Tim S.
Pages: 1 2 [3] 4 5 6 7 8 ... 10