GDB/MI (Was: Embedded development)
roberto at kdevelop.org
Tue Sep 13 10:37:03 UTC 2005
In KDevelop4 I would like to split the GUI from the GDB-support. The idea is
to reuse the GUI to integrate different debuggers. As I said before I want to
avoid code duplication and cut&paste int KDevelop4.
About the GDB-support. I know GDB/MI is incomplete and we need to mix
GDB/shell commands and GDB/MI commands, but to me it sounds like the _right_
(tm) tecnology to use. What do you think about GDB/MI and integrate it in
A couple of years ago I wrote a simple GDB/MI analyzer and Alexander
implemented a simple debugger with it. Unfortunatly he deleted the
Debugger :-) maybe we can use this experience to re*design/develop* it
Alexander?, Vladimir? John? :-)
On Tuesday 13 September 2005 09:29, Vladimir Prus wrote:
> On Tuesday 13 September 2005 00:06, Alexander Neundorf wrote:
> > > 1. A clear goal or mission statement ie, "To offer the best KDE/Qt
> > > development environment bar none." I think focusing on such a mission
> > > statement will provide a better direction for thinking about what we
> > > want to see in the new kdevelop.
> > I use it for embedded development, the "best KDE IDE" is not
> > automatically the tool of choice for me.
> BTW, any ideas about possible improvements of KDevelop debugger for
> embedded development are very welcome. I'm now trying to debug something
> remotely, and setting things is much harder that it should be.
> BTW, I'm also trying to create nicer register viewers that have to be
> specific for a processor architecture, along the lines of
> Probably we can arch-specific views for a couple of popular embedded
> processors (say, ARM and MIPS, don't have any popularity figures).
> - Volodya
> KDevelop-devel mailing list
> KDevelop-devel at barney.cs.uni-potsdam.de
More information about the KDevelop-devel