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

Vladimir Prus ghost at cs.msu.su
Mon Jun 6 17:20:07 UTC 2005

On Monday 06 June 2005 17:31, Richard Dale wrote:

> > 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?

Ok, I've found 'ruby' installed here and tried the debugger with this program:

threads = []
6.times { |i|
  threads << Thread.new(i) {
    raise "Boom!" if i == 3
    puts i
threads.each {|t| t.join }

I set breakpoint on the "raise" line and run it. The framestack widget shows
some threads, one is opened and others are closed. When I click on a "+" near 
closed thread, the framestack windows disappears and the first frame of the 
selected thread appears to be selected. That's behaviour my patch is trying 
to fix for C++ debugger.

- Volodya

More information about the KDevelop-devel mailing list