Re: Understanding GDB frames

[Jim Ingham <jingham@apple.com>]

I don't see what the bad effect of not destroying the varobj if the  
frame id is identical is. You might get an errant "value changed"  
notification.  Other than that, I can't see what you would be gaining.

If we're going to do some extra work to make sure we mark variables  
out of scope when their frames are exited, we should get something  
real out of it.  So far it seems the benefit is only theoretical.

Jim

On May 22, 2007, at 9:36 AM, Daniel Jacobowitz wrote:

> On Tue, May 22, 2007 at 09:10:29AM -0700, Marc Gauthier wrote:
>> As we discussed offline yesterday, this has performance implications
>> on the GUI, which would have to recreate the varobjs every time which
>> is time consuming.
>
> Is the performance implication the main reason?  If so, I'd rather we
> fix that instead.  I know Nick and/or Vladimir suggested "-var-list
> --locals" at one point in an earlier discussion of a related problem.
> That's probably quite a lot faster, especially if we can notify the
> front end when it enters a new frame.
>
> -- 
> Daniel Jacobowitz
> CodeSourcery