How to start KDevelop in GDB nowadays?

[Aleix Pol]

Well we can always attach to it, but there are cases where it won't be
enough.

On Mon, Dec 21, 2009 at 5:45 PM, Andreas Pakulat <apaku at gmx.de> wrote:

> On 21.12.09 16:00:05, David Nolden wrote:
> > Am Montag 21 Dezember 2009 15:45:12 schrieb Milian Wolff:
> > > Hey all!
> > >
> > > How do I start kdevelop inside GDB nowadays? That kdev_starter always
> > >  insists on spawning new processes in the background and doesn't come
> with
> > >  a -debug / - nofork switch...
> >
> > Either attach to the process, or set a KDEV_SESSION="{...}" environment
> > variable.
>
> Hmm, doesn't gdb's "follow-childs" mode work too?
>
> Of course this makes it quite a bit harder to debug startup-problems. I'm
> still not satisfied with this change (but I also don't have a better idea
> at the moment, except dropping global statics from the duchain).
>
> Andreas
>
> --
> Everything will be just tickety-boo today.
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20091221/0f18a36f/attachment.html>