[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Zylin embedded CDT plugin hacks
|
At 04:44 PM 6/22/2005, Alain Magloire wrote:
> resurrection of (gdb) prompt +
> various minor stuff.
>
That is more tricky. The thing is the console view is rather ...
difficult to use(read not intuitive) for example the cursor
must be a the rigth position before you are able to type in ...
there is no histor, no completion etc ....
John Cortell and some other folks are proposing to have a __real__
command line interface and views and the folks at Eclipse debug
seems also to be open at the idea ... so ... future looks good.
I'll take this as an opportunity to submit some further thoughts that a
colleague and myself have come up with on the subject.
One approach that might make sense is to have CDT provide a CDT-specific
command console while letting (maybe 'expecting' is a better word here) the
back-ends to optionally provide a console that is specific to the back-end.
The idea here is that the CDT console will be a common denominator cmdline
driver for CDT debug sessions. Like a good politician, it will try to
please everyone, but in the process will fail to meet some very specific
needs of most. It will be a command line access point for all the
functionality CDT and the platform provides, and this may cover 90-95% of
what real-world users need. However, some users may want/need cmdline
accessibility that is more back-end specific. This may be because the user
is more comfortable driving the session that way, or because the user wants
to exercise features only available that way.
One specific back-end console is the dgb console. For Freescale, it's the
CodeWarrior Command Window. I could see these co-existing with the future
CDT debug console window. Not to say that the user should try to drive a
debug session with both at the same time, but certainly it would be nice to
give the user the option of to use either, and perhaps even go back and
forth if that can be supported.
A variation of this idea is to simply allow the back-ends to add custom
comands to the CDT debug console window, rather than provide the user with
two types of consoles. After discussing the pros and cons, though, we had
some significant doubts that this would work smoothly.
Anyway, those are some high-level thoughts. More to come down the road...
John
