Recent Posts

Pages: 1 ... 3 4 5 6 7 [8] 9 10
71
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.
72
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
73
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.
74
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.
75
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
76
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".
77
Use the built-in Resource Monitor, see the second answer in this post for a guide.
78
The "No project/No target/Unknown compiler" message has no sense, and

That means the OP is not using an CB project.

Tim S.
79
Yes. It's not there (it disappears when I close the terminal window, as expected).

I also downloaded process explorer and tried to search for processes under that name, or any other meaningful name I could think of, cannot find anything .. I also searched on how to list all running processes via powershell and sort them by datetime for example (show most recent on top so i don't get lost), again I can see the process (name, pid, everything) when the terminal window is open, but when i close it there seems to be no process kept running that could somehow explain 'locking' test3.exe ...

80
Did you verify in the Windows task manger that test3.exe is not still running?

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