Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

[New plugin] cbSystemView for embedded development

<< < (6/6)

BlueHazzard:
Ok, i tested it now and it seems to work on windows 7.

The plugin still needs some tweaks, but the api is fine and should work!

great!

BlueHazzard:
The problem with the debugger i had, by not be able to send a ctrl+c to the gdb trough codeblocks was because i run codeblocks with codeblocks... If i run codeblocks directly i am able to send the ctrl+c....

Not working:

--- Code: ---codeblocks->codeblocks->arm_gdb->arm_gdb_server
--- End code ---
working:

--- Code: ---codeblocks->arm_gdb->arm_gdb_server
--- End code ---
this has probably something to do with the executable group... I think at some time we need to introduce a proxy program for gdb.... (also the 32bit <-> 64 bit thing would be solved by this) but this is for later...

oBFusCATed:
What do you mean by proxy program? On windows any gdb which supports python is setup to start two executables gdb and gdb_orig... This causes lots of problems...

ollydbg:

--- Quote from: oBFusCATed on April 23, 2019, 08:29:12 am ---On windows any gdb which supports python is setup to start two executables gdb and gdb_orig...

--- End quote ---
I think only GDB supplied from mingw-w64(original name is mingw-build) has such two gdb executables. I don't know why they need such changes, maybe they want to load the python pretty printer automatically by the proxy-gdb.

For me, I use GDB build myself, I don't use such proxy-gdb. ;)

oBFusCATed:
The gdb from tdm I had also had these two executables and yes they probably use it to setup correct python environment. But this is not what CB expects and there are problems.

Navigation

[0] Message Index

[*] Previous page