debugging kdevelop.bin doesn't work
apaku at gmx.de
Thu Feb 25 08:23:43 UTC 2010
On 25.02.10 07:00:25, Niko Sams wrote:
> On Tue, Feb 23, 2010 at 22:39, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 23.02.10 22:01:57, Niko Sams wrote:
> >> On Sun, Feb 21, 2010 at 19:17, Andreas Pakulat <apaku at gmx.de> wrote:
> >> > Hi,
> >> >
> >> > seems like debugging kdevelop with kdevelop is currently not possible.
> >> > I've setup a launch config that uses "app/kdevelop.bin" target as
> >> > executable and created+selected an environment that sets KDEV_SESSION to
> >> > a session-id. Unfortunately starting the debugger just "exits normally".
> >> > This almost looks like when one specifies app/kdevelop, which forks the
> >> > real app.
> >> >
> >> > Anybody else seeing this? Do I have something wrong?
> >> With the changes Alexander commited last week debugging kdevelop directly
> >> works just fine.
> > Well, that didn't work either, thats why I tried kdevelop.bin+envvar. So
> > how do I debug this?
> Strange; it works for me. Double checked now on my desktop machine.
> gdb kdevelop
> hit Ctrl+C
> stops somewhere in main_internal.cpp
> maybe you have the follow child processes commands enabled?
I'm not talking about standalone-gdb, I want to debug kdevelop from
inside kdevelop. I had a breakpoint on a kcm-constructor and it wasn't
triggered when I opened the config page.
You're a card which will have to be dealt with.
More information about the KDevelop-devel