[cdt-debug-dev] Re: cdt-debug-dev digest, Vol 1 #223 - 9 msgs

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

> Thanks for your answers,
> 
> I will have a look at the way that yvind Harboe used to deal with his arm
> target during the next days. (I expect to need to spend some time on more
> *basic* problems in order to understand more clearly the mechanism of how
> CDT launches the debugger. I so far have avoided to look at the CDT
> sources.)

My plan is to build, and make available for download, a hacked up CDT
plugin from CVS HEAD with the changes I outlined. That plan has so far
been foiled by various hickups in the build process, that most likely
are resolved early next week. 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=62872



> In order to understand more clearly please allow me to ask three additional
> (possibly stupid) questions:
> 
> 1.) Concerning MI interface: I understood that in case that you take the gdb
> sources from the gnu site and compile them for your target platform, you can
> assume that the MI interface support already is included.? At least I
> understood that yvind Harboe's arm-gdb already had MI-support. Is this
> correct?

I think yes. There is nothing special about arm-elf-gdb that I'm using.
It is part of the precompiled binary toolchain that eCos provides.


> 2.) Concerning the patches of yvind Harboe: I understood that your patch
> basically gives the user the possibility to use the gdb command line in
> order to use its flexibility to issue instructions that usually are not
> necessary. I.e. commands that are not required unless you are dealing with
> remote target systems or other non-standard debugging tasks. Did I
> understand correctly ?

It is simpler than that:

The first thing CDT *always* do is execute a GDB "run" command. 

With my patch, CDT no longer issues "run" when starting debugging, and
you have to enter itself manually in the GDB command line.

Or, you can enter any other incatation to set up your debug target.

> 3.) For debugging purposes: Is there an easy way to find out what CDT does
> when it is trying to establish the connection to the debugger? 

With my patch CDT does nothing after it connects to the debugger:
the debugger is left in idle mode, and you can attach to your target any
way you want. :-)


-- 
Øyvind Harboe
http://www.zylin.com