User forums > Using Code::Blocks

GDB

<< < (3/8) > >>

scarphin:
I understand that this works after GDB has been run and not available if GDB is not running. If that's the case, how can the GDB Server be fired before GDB tries to connect to it?

cbuser405:

--- Quote ---If that works I can implement it in the plugin or I can remove additional shell commands GUI and I can put some info how to do use the shell commands.
--- End quote ---
OK. It works.

Could you add a check box "use extended-remote" to configuration page for GDB RemoteConnection:
if not checked - works as before (send target remote)
if checked - send target extended-remote.

That would be the best solution.

Thank you!

oBFusCATed:

--- Quote from: cbuser405 on February 11, 2011, 03:37:22 pm ---OK. It works.

--- End quote ---
What do you prefer, combined list or two separe lists (probably I should check CDB) ?


--- Quote from: cbuser405 on February 11, 2011, 03:37:22 pm ---Could you add a check box "use extended-remote" to configuration page for GDB RemoteConnection:
if not checked - works as before (send target remote)
if checked - send target extended-remote.

--- End quote ---
Is this per project or global setting?

scarphin:
Well it doesn't work here. I used the command line below in the additional GDB commands before connection:

--- Code: ---shell cmd "avarice -g -j USB -P $(MCU) -j usb localhost:4242"
--- End code ---
and there is no sign of 'avarice' being fired which is the GDB Server for avr. It's in the path btw.

scarphin:
It seems it's not implemented in the AVR target.
http://linux.die.net/man/1/avr-gdb

I still don't understand why the 'additional shell commands' can't have the same implementation like the 'Tools' menu?

Navigation

[0] Message Index

[#] Next page

[*] Previous page