[PATCH] Re: Bug 68015: Variables/Watch Window closes on first view

Richard Dale Richard_Dale at tipitina.demon.co.uk
Mon Jun 6 16:36:05 UTC 2005

On Monday 06 June 2005 14:14, Vladimir Prus wrote:
> On Monday 06 June 2005 13:50, Richard Dale wrote:
> > > With my patch, at step 2 we don't issue selectFrame signal, so (3) does
> > > not work. I propose the following revised patch -- the only difference
> > > is that the actOnProgramPause now unconditionally issues "info locals".
> >
> > Has anyone looked at the ruby debugger code and compared it with the gdb
> > one? The code was derived from gdbcontroller, but I fixed quite a few
> > issues like this as far as I can remember. Anyone familiar with
> > gdbcontroller should find it easy to understand. It can display multiple
> > frames on each step, which can be open or closed. It only fetches local
> > variables for an open frame. And multiple frames persist between steps,
> > until they go out of scope.
> Looking at your code, it looks like it still has the same problem. If I
> open a thread in framestackview, the selectFrame signal is emitted, and
> rdbcontroller end up emitting showStepInSource -- which is exactly what I'm
> trying to avoid. Did I miss something?
You say ' Looking at your code', but I can't remember any problem with this 
specific issue. Can you try it out in practice and see if there is a problem?

-- Richard

More information about the KDevelop-devel mailing list