Author Topic: Configuring GDB to debug remotely  (Read 5200 times)

wayne

  • Guest
Configuring GDB to debug remotely
« on: July 20, 2006, 05:48:14 pm »
Hi,

Is there a way of configuring GDB via C::B to debug a remote platform ?
I've configured the IDE to recognise gdb and invoke it but the manner it does
it, by default, doesn't suit the debugging a piece of hardware at the end of
a serial port.

To debug remotely we initialise the hardware and purposely call GDB trap this
allows gdb to connect to the hardware. When connecting to the hardware via
C::B on the Debug menu, the only relevant option of the menu thats enabled
is 'Start' - this performs the GDB connection we require (debug levels, baud
rate, symbol load) but also seems to issue a run command. Is there anyway
to stop the run command being issued ?

I notice that the IDE configures gdb to intel flavour disassembley - is there a
configuration menu I haven't found to change this sort of operation.

I'm using the CB_20060719_rev2772_win32.7z nightbuild.

thanks

Wayne


Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Configuring GDB to debug remotely
« Reply #1 on: July 20, 2006, 06:05:15 pm »
Is there anyway to stop the run command being issued ?
Not currently, but you can send commands to the debugger if that is of help (Menu "Debug" -> "Send user command too debugger").

I notice that the IDE configures gdb to intel flavour disassembley - is there a
configuration menu I haven't found to change this sort of operation.
Again: not currently.

Anyway, I see the point and these are in fact interesting issues that could be implemented. Would you be so kind to file a feature request at the BerliOS webpage accordingly? Thus these requests don't get lost and we can talk about them when mandrav (he more-or-less in charge of the debugger plugin) is back.

With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Configuring GDB to debug remotely
« Reply #2 on: July 20, 2006, 09:22:18 pm »
Ok, I've done it in SVN. Tomorrow's nightly will have both options available (implemented).
(I had nothig better to do... ;-))
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

wayne

  • Guest
Re: Configuring GDB to debug remotely
« Reply #3 on: July 21, 2006, 03:09:16 pm »
Ok, I've done it in SVN. Tomorrow's nightly will have both options available (implemented).
(I had nothig better to do... ;-))

Hi Morten - that was fast work ! I'll download the release when its available, thanks for the response.

One thing I noticed with the 'send command to debugger' option, is: its only enable once the debugger
has been 'started' this prevents the user issuing discrete connect commands to the debugger without
first issuing a 'start' command to get the menu option to be enabled.

I have connected to the debugger using the 'send command to debugger' option and it does seem to
work.

thanks

Wayne

mifi

  • Guest
Re: Configuring GDB to debug remotely
« Reply #4 on: July 24, 2006, 09:20:56 pm »
Hello Morten,

perhaps you can help me too.

I try to use the debbuger for an ARM target.

I get a connection with my target, but the debugger want to
use the "run" command. Where can I disable these commands
because the arm-elf-gdb does not support "run".

I am using CB Build: Jul 23 2006

Best regards,

Michael


Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Configuring GDB to debug remotely
« Reply #5 on: July 24, 2006, 09:55:40 pm »
I get a connection with my target, but the debugger want to
use the "run" command. Where can I disable these commands
because the arm-elf-gdb does not support "run".
Please goto menu "Settings" -> "Compiler and Debugger" -> select "Debugger settings" and enable "Do *not* run the debugee".
With regards, Morten.

Ps: This requires at least revision 2776.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ