Debugger in trunk/ vs. playground/

[Andreas Pakulat]

On 14.04.09 12:36:50, Vladimir Prus wrote:
> On Monday 13 April 2009 14:26:03 Andreas Pakulat wrote:
> > On 13.04.09 10:12:43, Niko Sams wrote:
> > > SVN commit 953054 by nsams:
> > > 
> > > - Add a Common Debugger Infrastructure to kdevplatform. This is only the beginning
> > >   as it only provides debugger actions for now.
> > > - Port gdb to that Common Debugger Infrastructure
> > >   Ported: actions, stack-model
> > 
> > Hmm, what do we do about the one in playground? Vladimir, will you have
> > time in the next say 3 months to bring the gdb support in trunk/ into a
> > state where:
> > 
> >  - start a c++ app
> >  - stop at a breakpoint
> >  - stepping (including single-step, step-into and step-out)
> >  - interrupting an app
> >  - showing stackframes+threads in a toolview
> >  - showing variables in a toolview
> >  - executing gdb commands from the gdb window
> >  - debug an app more than once without restarting
> > 
> > will work? (Note, I'm not saying any of these don't work, I didn't test,
> > this is just a list of things that IMHO need to work for the next beta).
> > 
> > If you don't have the time please let us know asap so we can port back
> > the relevant changes from the debug-framework from trunk to the
> > playground gdb-plugin and switch the two again.
> 
> I believe I will. Specifically, showing variables in the primary problem
> at the present -- I intend to implement necessary GDB-side changes before
> GDB branches for 7.0 -- May 8, and implement, in parallel, necessary
> KDevelop hooks. After that, we'll "only" need to do some polishing,
> and I don't have any big deadlines until Fall, so should have the time.

Ok, thanks. Then lets keep things as they are now.

Andreas

-- 
Just to have it is enough.