debugging kdevelop.bin doesn't work

[Niko Sams]

On Thu, Feb 25, 2010 at 09:23, Andreas Pakulat <apaku at gmx.de> wrote:
> 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
>> run
>> ....wait
>> 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.
That works for me too.
I started like that:
kdevelop --debug gdb kdevelop -s test
the (automatically added) breakpoint in main was hit once in main.cpp
and once in main_internal.cpp.
I could add additional breakpoints and kdevelop stopped there.

Did you try using gdb from console? First we should figure out if it's
an gdb or kdevelop only issue.

Niko