[cdt-debug-dev] SV: cdt-debug-dev digest, Vol 1 #164 - 1 msg

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

>3. CDT user FAQ suggests fro embedded debugging to use 'remote' target.
>I think that this is not applicable in the case of BDM, but may be I am
wrong?

Suggestion:

Do not use the CDT GDB remote target, use the "GDB debugger" target
instead.

In your .gdbinit file you then execute the GDB commands to attach to the
target, e.g.:

target remote 192.168.222.200:2001
monitor this
monitor that
set $pc=0x15e2135235
continue


That way you remove CDT from equation when attaching to the target. Works
like a charm for me(ref earlier postings).

One of my hobby horses is to try to convince the CDT guys that they should
add a "GDB embedded" debug target where they do not assume that GDB is
in the attached stated w/application loaded, but leave it to the developer
to write his own gdbinit or issue the commands to load/start the application
manually. Plus it seems silly that all embedded developers have to edit
plugin.xml, so the "GDB embedded" should have a cpu="all" in plugin.xml.


Øyvind