KDE/kdevplatform

Andreas Pakulat apaku at gmx.de
Fri Apr 24 22:16:03 UTC 2009


On 24.04.09 23:59:43, Aleix Pol wrote:
> On Fri, Apr 24, 2009 at 11:37 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 24.04.09 23:15:46, Aleix Pol wrote:
> > > On Fri, Apr 24, 2009 at 11:05 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > > > On 24.04.09 19:56:40, Aleix Pol Gonzalez wrote:
> > > > So we have one view for threads and one for the stack? I'd find it
> > nicer
> > > > if both where in the same tree, having a stack under each thread (if
> > the
> > > > thread is not running)
> > > >
> > > Both were in the same tree before and it was not really good, having it
> > > separed it lets us to have some nice features (like automatically growing
> > > the stack)
> >
> > Not sure I understand why growing the stack automatically is not
> > possible in a tree.
> 
> Well, you would never know what leaf of the tree you want to grow, and it
> would not be logical.

Hmm, I must be missing something. Lets say I've got an app with three
threads, one of them is halted, the others are running. Then the tree is
this:

Thread 1
Thread 2
 |
 - topfunction
 - nextfunction
 - nextfunction
Thread3

Now if I jump either into the next deeper function or out of topfunction
you change the subtree under Thread2. As soon as one of the other
threads hits a breakpoint, the breakpoint is activated, you switch the
source file and expand the threads stack.

So, what am I missing?

Andreas

-- 
Don't read everything you believe.




More information about the KDevelop-devel mailing list