GDB Variables/Watches

Niko Sams niko.sams at gmail.com
Sun Jun 14 12:29:33 UTC 2009


On Sat, Jun 13, 2009 at 19:32, Andre
Poenitz<andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> On Sat, Jun 13, 2009 at 09:41:26AM +0200, Niko Sams wrote:
>> Hi,
>
> Hi Niko.
>
>> The main missing part of our current gdb debugger is a properly
>> working variable view.
>>
>> I took the qt-creators implementation of Watches (how they call them)
>> and started porting it to kdevelop.
>> Including splitting up debugger independent stuff into the platform.
>> It compiles and locals are shown correctly during debugging. But still
>> a long way to go.
>>
>> Before I put more time into this I want to ask what you think about it.
>
> You are certainly well within your rights that the LGPL gives you here
> and I probably should feel honoured to a certain degree - even if I have
> rather opposite feelings right now. Should not matter for you, though...
>
> Anyway, a word of caution: The variable view and especially the update
> mechanism is one of the most unreliable and also slowest parts of
> Qt Creator's gdb frontend.
hmm, good to know...
I decided to stick with our implementation for now anyway. Especially
after I saw
the python scripting for pretty printing.

Niko




More information about the KDevelop-devel mailing list