Recent Posts

Pages: 1 [2] 3 4 5 6 7 ... 10
11
Help / Re: debugger_gdbmi
« Last post by Pecan on May 03, 2026, 09:33:13 pm »
Quote from: Frank_CB on May 03, 2026, 08:42:30 pm
Setting cb_plugin to '.' (without quotes) also fails. Codeblocks issues a warning about not being able to locate the variable. Build log follows:

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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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), 6 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), 7 second(s))
 
Process terminated with status 0 (0 minute(s), 12 second(s))
2 error(s), 0 warning(s) (0 minute(s), 12 second(s))
 
The problem is not the cb_plugin variable.
The problem is that the .cbp is are not correctly pointing to the CodeBlocks source in your project .cbp.

Do the following:
In a console (cmd.exe) issue the following commands:
Code
cd  c:\CB13840
tree

copy and paste the results here.

12
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 03, 2026, 08:42:30 pm »
Setting cb_plugin to '.' (without quotes) also fails. Codeblocks issues a warning about not being able to locate the variable. Build log follows:

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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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:\CB13840\..\include -Ic:\CB13840\..\include\tinyxml -Ic:\CB13840\..\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:\CB13840\..\.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), 6 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), 7 second(s))
 
Process terminated with status 0 (0 minute(s), 12 second(s))
2 error(s), 0 warning(s) (0 minute(s), 12 second(s))
 
13
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 03, 2026, 08:07:23 pm »
debugger_gdbmi_wx33_64.cbp
14
Help / Re: debugger_gdbmi
« Last post by Pecan on May 03, 2026, 07:52:51 pm »
Quote from: Frank_CB on May 03, 2026, 08:33:54 am
@Pecan:
What value would you assign to cb_plugin ?

CodeBlocks should not be asking you for that variable. It's left over from when AndrewCott used to create a .plugin file.

If it's asking you for a value, just give it a '.' (period without the quotes).

Tell me which .cbp file you're using to build the project so I can correct this.
15
Plugins development / Re: Debugger_gdbmi plugin
« Last post by Pecan on May 03, 2026, 06:57:38 pm »
Quote from: ollydbg on May 03, 2026, 05:09:52 pm
Code
[debug]ActionsMap::Run -> starting action: 0000000011aa5f50 id: 21
[debug]cmd==>210000000000-var-update 1 *
[debug]output==>210000000000^done,changelist=[{name="var5",value="std::vector of length 5, capacity 5",in_scope="true",type_changed="false",new_num_children="5",displayhint="array",dynamic="1",has_more="0"}]
[debug]cmd==>210000000001-var-list-children 2 "var5"
[debug]unparsable_output==>(gdb)
[debug]output==>210000000001^done,numchild="5",displayhint="array",children=[child={name="var5.[0]",exp="[0]",numchild="0",value="1",type="int"},child={name="var5.[1]",exp="[1]",numchild="0",value="2",type="int"},child={name="var5.[2]",exp="[2]",numchild="0",value="3",type="int"},child={name="var5.[3]",exp="[3]",numchild="0",value="4",type="int"},child={name="var5.[4]",exp="[4]",numchild="0",value="5",type="int"}],has_more="0"
[debug]unparsable_output==>(gdb)


question:

Is the "unparsable_output" correct? See the above log.

Yes. It's ok. It's left over from code inherited from the original CodeBlocks debugger plugin.
I seem to remember that I tried to eliminate it, but removing it just caused a whole bunch of problems.

The original debugger code set that line as the prompt to be sent back from from gdb.
On some commands to gdb, there is original plugin code that waits for multiple responses to be returned to CodeBlocks; debugger plugin goes idle before sending any more commands. The idle condition is keyed to that prompt to indicate the end of any more responses and clears the idle condition.

Since the original debugger code and prompt mechanism worked with debugger_gdbmi (and caused problems without it), I got lazy and just left it for now.

I'll put this in the "revisit latter" ToDo queue. I'd also like to eliminate it if I can.

16
Plugins development / Re: Debugger_gdbmi plugin
« Last post by ollydbg on May 03, 2026, 05:09:52 pm »
Code
[debug]ActionsMap::Run -> starting action: 0000000011aa5f50 id: 21
[debug]cmd==>210000000000-var-update 1 *
[debug]output==>210000000000^done,changelist=[{name="var5",value="std::vector of length 5, capacity 5",in_scope="true",type_changed="false",new_num_children="5",displayhint="array",dynamic="1",has_more="0"}]
[debug]cmd==>210000000001-var-list-children 2 "var5"
[debug]unparsable_output==>(gdb)
[debug]output==>210000000001^done,numchild="5",displayhint="array",children=[child={name="var5.[0]",exp="[0]",numchild="0",value="1",type="int"},child={name="var5.[1]",exp="[1]",numchild="0",value="2",type="int"},child={name="var5.[2]",exp="[2]",numchild="0",value="3",type="int"},child={name="var5.[3]",exp="[3]",numchild="0",value="4",type="int"},child={name="var5.[4]",exp="[4]",numchild="0",value="5",type="int"}],has_more="0"
[debug]unparsable_output==>(gdb)


question:

Is the "unparsable_output" correct? See the above log.
17
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 03, 2026, 08:33:54 am »
@Pecan:
What value would you assign to cb_plugin ?
18
Plugins development / Re: Small problem in DragScroll_Windows.cbp
« Last post by jggimi on May 03, 2026, 06:01:04 am »
13840 resolved my problem.  Thanks!!
19
Plugins development / Re: Small problem in DragScroll_Windows.cbp
« Last post by Pecan on May 02, 2026, 11:17:50 pm »
Quote from: killerbot on May 02, 2026, 06:14:37 pm
also on linux things seem to be broken:

make[4]: *** No rule to make target 'manifest.xml', needed by 'dragscroll.zip'.  Stop.

Fixed svn 13840
20
Help / Re: debugger_gdbmi
« Last post by Pecan on May 02, 2026, 07:17:14 pm »
Quote from: 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.

I extracted the changes from your PR and added them manually, Thanks.
It does not appear that the .wxs file is needed. I don't find it anywhere in the whole of CodeBlocks.
That .wxs line may be left over from the original codeCompletion .cbp that I copied.

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