Tooltip when debugging

Vladimir Prus ghost at cs.msu.su
Mon Feb 23 14:13:18 UTC 2009


On Monday 23 February 2009 17:00:47 Aleix Pol wrote:
> On Mon, Feb 23, 2009 at 2:50 PM, Vladimir Prus <ghost at cs.msu.su> wrote:
> 
> > On Monday 23 February 2009 16:44:16 Mario Chacon wrote:
> > > On Mon, Feb 23, 2009 at 11:18 AM, Vladimir Prus <ghost at cs.msu.su> wrote:
> > >
> > > > On Monday 23 February 2009 15:57:50 Mario Chacon wrote:
> > > > > On Mon, Feb 23, 2009 at 9:57 AM, Vladimir Prus <ghost at cs.msu.su>
> > wrote:
> > > > >
> > > > > > On Monday 23 February 2009 13:46:48 Mario Chacon wrote:
> > > > > > > Hello:
> > > > > > > Is it possible to make like Visual studio that when you are debug
> > in
> > > > and
> > > > > > you
> > > > > > > stop over a variable you sow the current value?
> > > > > >
> > > > > > What do you mean by "stop over a variable"?
> > > > > >
> > > > >
> > > > > sorry, no when you stop, what I want to tried to said is: when you
> > are
> > > > debug
> > > > > in and put mouse course over a variable. it's show the current value,
> > Is
> > > > it
> > > > > possible to make it in kdevelop4?
> > > >
> > > > This is exactly what we are discussing in this thread. It's possible in
> > SVN
> > > > HEAD
> > > > of KDevelop4.
> > > >
> > >
> > >  great!!..If it's an string data, will be show the value directly ??
> >
> > I don't know. The hack that was used for QString display in KDevelop3 may
> > not
> > be ported yet, and in fact, it won't be ported ever. Upcoming GDB 7.0 uses
> > Python
> > scripting to visualize classes, and that covers std::string, std::vector
> > and others.
> > We'll just add QString visualizer.
> 
> 
> >
> > - Volodya
> >
> > _______________________________________________
> > KDevelop-devel mailing list
> > KDevelop-devel at kdevelop.org
> > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> >
> 
> When are we going to have gdb 7.0?

The branch is scheduled for 2009-05-08 and release is scheduled for 2009-06-05.
I'll see if KDevelop4 debugger can be made to work acceptably with 6.8, but advanced
functionality such as STL display will need 7.0 (or manually built gdb).

> We will still be able to use the gdb script in kdesdk/scripts and it will
> work, isn't it?

Yes.

- Volodya




More information about the KDevelop-devel mailing list