What's missing for 4.0
Andreas Pakulat
apaku at gmx.de
Thu Sep 17 19:27:34 UTC 2009
On 18.09.09 00:41:56, Kishore wrote:
> On Thursday 17 Sep 2009 11:51:50 pm Andreas Pakulat wrote:
> > > 1. The debugger is essentially unusable, even for local debugging (and
> > > I really need remote debugging facilities). I realize that that's
> > > being worked on.
> >
> > I'm not sure wether remote debugging will make it into 4.0.
> >
>
> Is remote debugging really very different? at least if it is using gdb? My
> daily work is with embedded systems and the only difference between them is in
> the way i launch gdb. For native apps, i execute "gdb path/to/app" and with
> remote system "arm-none-eabi-gdb -x path/to/gdbinit path/to/app".
>
> Rest is all the same it seems. I recently tried debugging a remote target
> using kdev4 and it did not work. I did not explore further but it does not
> seem like a great deal as long as one can configure the gdb executable and
> some launch parameters. I did try that in the gdb configuration, but it did
> not seems to work and i don't know why. It works fine in kdev3.
Well, it'll only work if that arm-none-eabi-gdb is built from gdb cvs
head and supports the MI interface. Apart from that, there's (AFAIK)
also some gdb + gdbserver kind of remote debugging (dunno details as I
don't use any of that).
Andreas
--
If you can read this, you're too close.
More information about the KDevelop-devel
mailing list