31
Help / Re: debugger_gdbmi
« Last post by ollydbg on May 02, 2026, 08:30:43 am »I have create a PR add Windows.cbp file by asmwarrior Pull Request #1 pecanh/debugger_gdbmi for your repo.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
32
Help / Re: debugger_gdbmi
« Last post by ollydbg on May 02, 2026, 07:25:41 am »One question: When I looked at the file: debugger_gdbmi_wx33_64.cbp
I don't see the wxs file in the github code repo, did you forget to add it to the repo?
EDIT1:
Or maybe, the config.h and config.cpp is not necessary for building this plugin?
EDIT2:
I think the debugger_gdbmi_wx32_64.depend those depends file should be removed from the code repo.
Code
<Extensions>
<envvars set="cb_plugin" />
<wxsmith version="1">
<gui name="wxWidgets" src="" main="" init_handlers="necessary" language="CPP" />
<resources>
<wxPanel wxs="wxsmith/config_panel.wxs" src="src/config.cpp" hdr="src/config.h" fwddecl="1" i18n="1" name="ConfigurationPanel" language="CPP" />
</resources>
</wxsmith>
</Extensions>
I don't see the wxs file in the github code repo, did you forget to add it to the repo?
EDIT1:
Or maybe, the config.h and config.cpp is not necessary for building this plugin?
EDIT2:
I think the debugger_gdbmi_wx32_64.depend those depends file should be removed from the code repo.
33
Development / Re: wxSmith use bad constructor for wxStaticBoxSizer
« Last post by ollydbg on May 02, 2026, 07:18:41 am »Using Delta Executor, users can experience smooth script execution with fewer errors. Its optimized system improves performance and ensures a stable environment, helping users complete tasks quickly without facing technical problems.
spam reported.
34
Plugins development / Small problem in DragScroll_Windows.cbp
« Last post by gd_on on May 01, 2026, 02:52:18 pm »After the move to a subfolder src of the dragscroll plugin code (svn 13836), at line 61 DragScroll_Windows.cbp, a src\manifest.xml should be there (not only manifest.xml). Other cbps are OK.
35
Help / Re: debugger_gdbmi
« Last post by Frank_CB on April 30, 2026, 06:15:17 am »Thanks for responding. I'll just wait until it shows up in source.
36
Help / Re: debugger_gdbmi
« Last post by Pecan on April 30, 2026, 04:46:46 am »Debugger_gbdmi failed to build
Using Windows 10 Pro (64)
Build Log:Code-------------- Build: default in debugger_gdbmi wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\actions.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\actions.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cJSON.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cJSON.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cmd_queue.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cmd_result_parser.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cmd_result_parser.o
In file included from C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.cpp:1:
C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.h:11:10: fatal error: globals.h: No such file or directory
11 | #include "globals.h"
| ^~~~~~~~~~~
compilation terminated.
Process terminated with status 1 (0 minute(s), 9 second(s))
In file included from C:\Temp\newdir\debugger_gdbmi\src\actions.h:6,
from C:\Temp\newdir\debugger_gdbmi\src\actions.cpp:1:
C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.h:11:10: fatal error: globals.h: No such file or directory
11 | #include "globals.h"
| ^~~~~~~~~~~
compilation terminated.
Process terminated with status 1 (0 minute(s), 10 second(s))
Process terminated with status 0 (0 minute(s), 14 second(s))
2 error(s), 0 warning(s) (0 minute(s), 14 second(s))
Envar cb created with base of C:\CB13834 prior to failure.
-Ic:\CB13834\..\include must not actually point to the CodeBlocks src folder.
37
Help / Re: debugger_gdbmi
« Last post by Frank_CB on April 30, 2026, 03:17:02 am »Debugger_gbdmi failed to build
Using Windows 10 Pro (64)
Build Log:
Envar cb created with base of C:\CB13834 prior to failure.
Using Windows 10 Pro (64)
Build Log:
Code
-------------- Build: default in debugger_gdbmi wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\actions.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\actions.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cJSON.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cJSON.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cmd_queue.o
g++.exe -Wextra -Wall -m64 -g -g -pipe -mthreads -fmessage-length=0 -fexceptions -std=gnu++23 -DHAVE_W32API_H -DBUILDING_PLUGIN -D__WXMSW__ -DWXUSINGDLL -DNOPCH -DwxUSE_UNICODE -D_WIN64 -DCC_NO_COLLAPSE_ITEM -DcbDEBUG -DDOLOGSNIP -g -std=gnu++23 -Ic:\CB13834\..\include -Ic:\CB13834\..\include\tinyxml -Ic:\CB13834\..\sdk\wxscintilla\include -Isrc -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -c C:\Temp\newdir\debugger_gdbmi\src\cmd_result_parser.cpp -o c:\CB13834\..\.obj33_64\plugins\contrib\debugger_gdbmi\src\cmd_result_parser.o
In file included from C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.cpp:1:
C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.h:11:10: fatal error: globals.h: No such file or directory
11 | #include "globals.h"
| ^~~~~~~~~~~
compilation terminated.
Process terminated with status 1 (0 minute(s), 9 second(s))
In file included from C:\Temp\newdir\debugger_gdbmi\src\actions.h:6,
from C:\Temp\newdir\debugger_gdbmi\src\actions.cpp:1:
C:\Temp\newdir\debugger_gdbmi\src\cmd_queue.h:11:10: fatal error: globals.h: No such file or directory
11 | #include "globals.h"
| ^~~~~~~~~~~
compilation terminated.
Process terminated with status 1 (0 minute(s), 10 second(s))
Process terminated with status 0 (0 minute(s), 14 second(s))
2 error(s), 0 warning(s) (0 minute(s), 14 second(s))
Envar cb created with base of C:\CB13834 prior to failure.
38
Help / Re: Trouble Complining CB with CB under Linux
« Last post by cppuser on April 29, 2026, 11:08:16 pm »ok I think, I know what is the issue with the debugger I did not close it properly the first time.
When I restart everything worked ok in debug.
But I got this, about the codeblocks_data_dir (see the attachment please)
So am I placing the --prefix in the select_target dialog?
When I restart everything worked ok in debug.
But I got this, about the codeblocks_data_dir (see the attachment please)
So am I placing the --prefix in the select_target dialog?
39
Help / Re: Trouble Complining CB with CB under Linux
« Last post by cppuser on April 29, 2026, 10:53:08 pm »Hi, I post on this post because I believe it is relevant, after a small search for explanation on the codeblocks files. Sorry if you want me to post in another thread please tell me.
I am trying to compile codeblocks and debug it with codeblocks installed version on linux mint.
I am familiar with wxwidgets,
but I have a question about the filenames just to be clear.
CodeBlocks_Windows.workspace //ok this is clear for windows.
CodeBlocks_wx30-unix.cbp
CodeBlocks_wx30-unix.workspace
CodeBlocks_wx32_64.cbp
CodeBlocks_wx32_64.workspace
CodeBlocks_wx32.cbp //?? is this for windows and 32 bits?
CodeBlocks_wx32-unix.cbp
CodeBlocks_wx32-unix.depend
CodeBlocks_wx32-unix.workspace
CodeBlocks_wx32.workspace
CodeBlocks_wx33_64.cbp
CodeBlocks_wx33_64.workspace
CodeBlocks_wx33.cbp
CodeBlocks_wx33.workspace
wx32 means wxwidgets version 3.2.x unix mean linux, does it mean also mac too? Or because there is no mac version there is no codeblocks workspace for this?
what is the "_64" for??
I am trying to dive into the source code of codeblocks.
I open and compile CodeBlocks_wx32-unix.workspace and it went ok. But to debug it, I am struggling here with codeblocks.
the debugger shows me this...
Adding source dir: /home/user01/openprojects/codeblocks/src/
Adding file: /home/user01/openprojects/codeblocks/src/devel32/codeblocks
Changing directory to: /home/user01/openprojects/codeblocks/src/devel32
Set variable: LD_LIBRARY_PATH=.:/home/user01/openprojects/codeblocks/src/devel32:/usr/lib/x86_64-linux-gnu:
Starting debugger: /usr/bin/gdb -nx -fullname -quiet -args /home/user01/openprojects/codeblocks/src/devel32/codeblocks
Setting SHELL to '/bin/sh'
done
Setting breakpoints
Debugger name and version: GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
At /home/user01/openprojects/codeblocks/src/src/app.cpp:370
At /home/user01/openprojects/codeblocks/src/src/app.cpp:372
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:373
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:374
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:372
At /home/user01/openprojects/codeblocks/src/src/app.cpp:1582
Cannot open file: ./csu/../csu/libc-start.c
At ./csu/../csu/libc-start.c:144
The weird thing is that the first time it debugged fine until one point then it stopped. !!! All the breakpoints do not exist in the second time.
is there any parameters on debug that I am missing?
I am trying to compile codeblocks and debug it with codeblocks installed version on linux mint.
I am familiar with wxwidgets,
but I have a question about the filenames just to be clear.
CodeBlocks_Windows.workspace //ok this is clear for windows.
CodeBlocks_wx30-unix.cbp
CodeBlocks_wx30-unix.workspace
CodeBlocks_wx32_64.cbp
CodeBlocks_wx32_64.workspace
CodeBlocks_wx32.cbp //?? is this for windows and 32 bits?
CodeBlocks_wx32-unix.cbp
CodeBlocks_wx32-unix.depend
CodeBlocks_wx32-unix.workspace
CodeBlocks_wx32.workspace
CodeBlocks_wx33_64.cbp
CodeBlocks_wx33_64.workspace
CodeBlocks_wx33.cbp
CodeBlocks_wx33.workspace
wx32 means wxwidgets version 3.2.x unix mean linux, does it mean also mac too? Or because there is no mac version there is no codeblocks workspace for this?
what is the "_64" for??
I am trying to dive into the source code of codeblocks.
I open and compile CodeBlocks_wx32-unix.workspace and it went ok. But to debug it, I am struggling here with codeblocks.
the debugger shows me this...
Adding source dir: /home/user01/openprojects/codeblocks/src/
Adding file: /home/user01/openprojects/codeblocks/src/devel32/codeblocks
Changing directory to: /home/user01/openprojects/codeblocks/src/devel32
Set variable: LD_LIBRARY_PATH=.:/home/user01/openprojects/codeblocks/src/devel32:/usr/lib/x86_64-linux-gnu:
Starting debugger: /usr/bin/gdb -nx -fullname -quiet -args /home/user01/openprojects/codeblocks/src/devel32/codeblocks
Setting SHELL to '/bin/sh'
done
Setting breakpoints
Debugger name and version: GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
At /home/user01/openprojects/codeblocks/src/src/app.cpp:370
At /home/user01/openprojects/codeblocks/src/src/app.cpp:372
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:373
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:374
At /home/user01/openprojects/codeblocks/src/src/app.cpp:375
At /home/user01/openprojects/codeblocks/src/src/app.cpp:372
At /home/user01/openprojects/codeblocks/src/src/app.cpp:1582
Cannot open file: ./csu/../csu/libc-start.c
At ./csu/../csu/libc-start.c:144
The weird thing is that the first time it debugged fine until one point then it stopped. !!! All the breakpoints do not exist in the second time.
is there any parameters on debug that I am missing?
40
Development / Re: Quickly fully expanding a project's tree
« Last post by Miguel Gimenez on April 29, 2026, 01:27:54 pm »You can use commit 13834 as reference. Regarding interest, a fully expanded tree is hardly desired.