Started to fixup cppdebugger in trunk/kdevelop

[Andreas Pakulat]

On 09.02.09 09:16:13, Vladimir Prus wrote:
> So, the plan is that after each thread/frame change or stop, KDevelop
> should ask GDB about local variables in the current scope,

This is -stack-list-locals in gdb mi,
right?

> and GDB
> will do, for each variable, one of those 3 things:
> 
>   1. create new variable object for a local variable and report it. Then,
>   we create new Variable instance and add it to model

Where variable object is what one can do manually with -var-create in
gdb mi?

> Now, the problem is that GDB-side solution is not coded yet, so what do we do
> now? I think that:

Yeah, I noticed that :)

> 1. It's safe to assume that we'll issue a GDB command at each step to get the
> list of locals.
> 2. We'll need to implement reuse of Variable instances as explained above, but
> this really depends on GDB.
> 
> So, right now it's OK to assume that all variables are dead at each step -- which
> is what you have done.

No, in fact what I did is re-use variables and variable-items all the
time. And I'm not removing variables at all right now. So if a variable
goes out of scope while stepping its not removed.

The question is: Is it easier/efficient enough, to simply remove all
variables that are not used for a watch each time we have a frame or
thread change. Or should we keep the existing code to re-use Variable's
and VariableItem's and check which of them are not in the list of locals
on each frame/thread change?

Andreas

-- 
You are scrupulously honest, frank, and straightforward.  Therefore you
have few friends.