GDB/MI (Was: Embedded development)

Roberto Raggi roberto.raggi at
Wed Sep 14 17:52:58 UTC 2005


On Tuesday 13 September 2005 11:16, Vladimir Prus wrote:
> Hi Roberto,
> > On Tuesday 13 September 2005 10:50, Vladimir Prus wrote:
> > > Yes, me too. But in fact, the only code duplication we have is with
> > > Ruby, and it will be hard to merge both debuggers. And I'm still
> > > sceptical of the idea that we can implement, say, Python debugger,
> > > using the same interface.
> >
> > well we have the java debugger to do.
> Cool. Anybody is planning to do that already?

It is a fork of the cppdebugger. Of couse as all the other forks it is unsable 
and unmaintained :-)

> Yea, stack frames and breakpoints are pretty much the same, and hopefully,
> for Java variables/watches won't be very different.
good :-)

> > > I think I'll try to use MI for one or two commands (say, getting
> > > variable value and memory content) and see how it goes.
> >
> > Sounds good to me. I'm not an expert, but I was playing with the GDB/MI
> > support of eclipse/CDT.. and I have to say it is pretty impressive.
> If you know some specific things they have and we miss, just file them in
> bug tracker ;-)
I will

> > I don't mind if you want to use something else or rewrite it from
> > scratch. qdbg was just a one hour project :-)
> Thanks, I'll have a look.
sure! I hope it can help you. 

ciao robe

More information about the KDevelop-devel mailing list