[cdt-debug-dev] Re: Using CDT as avr-gdb frontent for AVR tar get

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

>I think that the solution is to use the current extension point to
>create a totally user customizable version of the debugger.  

Please induldge me when I get up on my soapboax:

The reason why the CDT debugger is in such dire straits(i.e. that stuff
that is trivial to do under GDB/DDD/Insight is darn hard under CDT), is
that CDT is not delegating the problems to the right "solution
paradigms".

Example of "solution paradigms":

- GUI
- GDB command line
- Plugins

* The problem of how to let the user examine local/global variables
should be handled by "GUI". Leaving it to "GDB command line" is a
painful.

* The problem of how to attach to the target should be handled by "GDB
command line".

If you give this problem to "GUI and Plugins", all hell breaks loose.

No harm is done by adding buttons to CDT that simply issue issue "target
remote foo", "run", "load", "continue", "attach 55" to GDB. This is what
DDD/Insight does. Attaching to target is still handled by "GDB command
line"

Be proud and embrace the GDB command line for it is powerful! :-)

Every command the user enters can take the debugger in a *completely*
different direction.


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