Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Using Code::Blocks / How prevent unfold code at closed brackets.
« Last post by squad on Today at 11:54:54 am »
It's a great IDE. Thanks. ;)

There's some folded code.
When I'm adding code before that folded section and accidentally type an right bracket(no left bracket, not closed.), all the folded code that follows gets expanded.
Is there any way to prevent this?
2
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by squad on Today at 11:47:08 am »
I am new, I am here. I am a human 8)
3
Help / Re: debugger_gdbmi
« Last post by Pecan on Yesterday at 04:28:25 pm »
Quote from: AndrewCot on Yesterday at 01:11:30 pm
Great work Pecan. Or in my words bloody good job (OZ).

One thing to remember is that testing is a killer and needs to be done using it against CB to fix bugs. It's a PITA an takes time.

The second thing to remember is no matter how good you think the debugger is there WILL be bugs slip through the corner cases or the homer effect (doh i did not check that or think to check that).

Overall I think in the short term this should go into the CB mainline to replace the existing GDB debugger as the existing GDB debugger uses the ancient and technically obsolete I/F.
But in the long term ..... move to the next one and save yourself the pain, unless ....... . At the end only you know the best way forward for yourself.

Good luck and keep up the great  work.

Thanks. I'm already working inside your DAP prototype.
It's a bitch. I hate that awful JSON parser.
I still don't understand what I have to do to define those To: and From: entries.
Praying to the code gods just does not work.

Even Gemini and Claude get confused and get it wrong.
But if I just try first (and always get it wrong) the robots can see how to fix it.
4
Help / Re: debugger_gdbmi
« Last post by AndrewCot on Yesterday at 01:11:30 pm »
Great work Pecan. Or in my words bloody good job (OZ).

One thing to remember is that testing is a killer and needs to be done using it against CB to fix bugs. It's a PITA an takes time.

The second thing to remember is no matter how good you think the debugger is there WILL be bugs slip through the corner cases or the homer effect (doh i did not check that or think to check that).

Overall I think in the short term this should go into the CB mainline to replace the existing GDB debugger as the existing GDB debugger uses the ancient and technically obsolete I/F.
But in the long term ..... move to the next one and save yourself the pain, unless ....... . At the end only you know the best way forward for yourself.

Good luck and keep up the great  work.
5
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 07, 2026, 11:50:49 pm »
Corrected lines 22 & 23 of my copy of debugger_gdbmi_wx33_64.cbp. Changed 32 to 33. The zip file is placed in the correct directory now.

Thanks!!
6
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 05, 2026, 07:09:17 pm »
@Pecan:
Thanks for providing the procedure for compiling the debugger_gdbmi plugin from source. I really hosed my first attempt at following it. My bad! I trashed those results and started from the beginning again. After adding the missing dll's, I was successful in compiling the plugin. Again, Thanks!!

Regards,
Frank
7
Plugins development / Re: Debugger_gdbmi plugin
« Last post by Pecan on May 05, 2026, 06:38:14 pm »
@ gd_on and ollydbg

acknowledge; watches problems put on top of the ToDo list.

also, I'll remove the gdbinit file from the github repo. It should not be there.

debugger_gdbmi tries to create the file dynamically if it finds gdbinit missing and it can find a valid wxWidgets installation folder which contains print.py.
If it finds gdbini already created, it leave it as is, assuming that the user created it themselves.

ollydbg's description of activated multiple debuggers is correct.
8
Plugins development / Re: Debugger_gdbmi plugin
« Last post by ollydbg on May 05, 2026, 02:33:08 am »
Quote from: gd_on on May 04, 2026, 08:04:30 pm
Last question : can we have both plugins (standard and gdmi) activated ? Or is it better to have only one activated (as for codecompletion and clangd_client) ?

Yes, you can have both of the 2 debugger plugins enabled. There is a menu item: Debug->Active debuggers->You can select one.


Quote
- with standard debugger, when I open the watches window, all my local variables are displayed. With gdbmi, I have to add one by one an explicit Watch to my local variables. I can then follow the content of my variables step by step when executing.
In the standard debugger plugin, this is the option: "Watch local variables". In the gdbmi plugin, I also see this option is ON, but I see the same issue here, which means local variables were not listed in the watches panel.

9
Help / Re: debugger_gdbmi
« Last post by Pecan on May 04, 2026, 11:26:33 pm »
Quote from: Frank_CB on May 04, 2026, 09:55:36 pm
Codeblocks.exe /d /p CBdevel executes now. Am having problem(s) with the compiler. It says that there is no linker.
Build Log
Code
-------------- Clean: Plugin - Win32 in Code Snippets wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------

Cleaned "Code Snippets wx3.3.x (64 bit) - Plugin - Win32"

-------------- Build: Plugin - Win32 in Code Snippets wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------

x86_64-w64-mingw32-g++.exe -Wall -m64 -g -pipe -mthreads -fmessage-length=0 -fexceptions -DWXUSINGDLL -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DcbDEBUG -DwxUSE_UNICODE -DBUILDING_PLUGIN -DNO_LOGGING std=c++23 -g -Winvalid-pch -DCB_PRECOMP std=c++23 -I..\..\..\include -I..\..\..\include\tinyxml -I..\..\..\sdk\wxscintilla\include -I..\..\..\src -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -I. -c C:\CBdevel\trunk\src\plugins\contrib\codesnippets\snippetsconfig.cpp -o ..\..\..\.objs33_64\plugins\contrib\codesnippets\plugin\snippetsconfig.o

x86_64-w64-mingw32-g++.exe -Wall -m64 -g -pipe -mthreads -fmessage-length=0 -fexceptions -DWXUSINGDLL -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DcbDEBUG -DwxUSE_UNICODE -DBUILDING_PLUGIN -DNO_LOGGING std=c++23 -g -Winvalid-pch -DCB_PRECOMP std=c++23 -I..\..\..\include -I..\..\..\include\tinyxml -I..\..\..\sdk\wxscintilla\include -I..\..\..\src -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -I. -c C:\CBdevel\trunk\src\plugins\contrib\codesnippets\codesnippets.cpp -o ..\..\..\.objs33_64\plugins\contrib\codesnippets\plugin\codesnippets.o

x86_64-w64-mingw32-g++.exe: warning: std=c++23: linker input file unused because linking not done
x86_64-w64-mingw32-g++.exe: error: std=c++23: linker input file not found: No such file or directory

x86_64-w64-mingw32-g++.exe: warning: std=c++23: linker input file unused because linking not done
x86_64-w64-mingw32-g++.exe: error: std=c++23: linker input file not found: No such file or directory

Process terminated with status 1 (0 minute(s), 27 second(s))

2 error(s), 2 warning(s) (0 minute(s), 27 second(s))
 

That "std=c++23" is suppose to be  "-std=c++23" (note the dash)
10
Help / Re: debugger_gdbmi
« Last post by Frank_CB on May 04, 2026, 09:55:36 pm »
Codeblocks.exe /d /p CBdevel executes now. Am having problem(s) with the compiler. It says that there is no linker.
Build Log
Code
-------------- Clean: Plugin - Win32 in Code Snippets wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------

Cleaned "Code Snippets wx3.3.x (64 bit) - Plugin - Win32"

-------------- Build: Plugin - Win32 in Code Snippets wx3.3.x (64 bit) (compiler: GNU GCC Compiler)---------------

x86_64-w64-mingw32-g++.exe -Wall -m64 -g -pipe -mthreads -fmessage-length=0 -fexceptions -DWXUSINGDLL -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DcbDEBUG -DwxUSE_UNICODE -DBUILDING_PLUGIN -DNO_LOGGING std=c++23 -g -Winvalid-pch -DCB_PRECOMP std=c++23 -I..\..\..\include -I..\..\..\include\tinyxml -I..\..\..\sdk\wxscintilla\include -I..\..\..\src -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -I. -c C:\CBdevel\trunk\src\plugins\contrib\codesnippets\snippetsconfig.cpp -o ..\..\..\.objs33_64\plugins\contrib\codesnippets\plugin\snippetsconfig.o

x86_64-w64-mingw32-g++.exe -Wall -m64 -g -pipe -mthreads -fmessage-length=0 -fexceptions -DWXUSINGDLL -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DcbDEBUG -DwxUSE_UNICODE -DBUILDING_PLUGIN -DNO_LOGGING std=c++23 -g -Winvalid-pch -DCB_PRECOMP std=c++23 -I..\..\..\include -I..\..\..\include\tinyxml -I..\..\..\sdk\wxscintilla\include -I..\..\..\src -IC:\wxWidgets-3.3.2\include -IC:\wxWidgets-3.3.2\lib\gcc_dll\mswu -I. -c C:\CBdevel\trunk\src\plugins\contrib\codesnippets\codesnippets.cpp -o ..\..\..\.objs33_64\plugins\contrib\codesnippets\plugin\codesnippets.o

x86_64-w64-mingw32-g++.exe: warning: std=c++23: linker input file unused because linking not done
x86_64-w64-mingw32-g++.exe: error: std=c++23: linker input file not found: No such file or directory

x86_64-w64-mingw32-g++.exe: warning: std=c++23: linker input file unused because linking not done
x86_64-w64-mingw32-g++.exe: error: std=c++23: linker input file not found: No such file or directory

Process terminated with status 1 (0 minute(s), 27 second(s))

2 error(s), 2 warning(s) (0 minute(s), 27 second(s))
 
Pages: [1] 2 3 4 5 6 ... 10