Re: -var-update and address changes

[Daniel Jacobowitz <drow@false.org>]

On Fri, Apr 14, 2006 at 12:49:05PM -0700, Jim Ingham wrote:
> Note as an aside, that we had to add another varobj type which is  
> evaluated in the selected frame, whatever that happens to be.  That  
> was useful for a general "variable inspector" window.  People wanted  
> to put some expression there, and have it re-evaluated in the topmost  
> frame whenever they stopped.  So we added that functionality.  But  
> that is clearly distinct from what the "*" varobj type is supposed to  
> mean.

Well, I interpreted it the other way around, so I'll dispute your
"clearly" :-)

> The fp part is just used as part of the frame fingerprint.  The pc is  
> used for other purposes of course (for instance if the disassembly  
> window is open), but the fp part is just used to check whether the  
> frame needs to be refreshed.  I have no problem with it being opaque.

It's the PC of the frame, not the current PC; I'm not sure why you'd
want to use it.  In any case, you can always fetch it for the frame,
or report it separately.  So, let's plan on using frame IDs in MI,
and defining them opaquely.  I'd even go so far as to make them strings
rather than numbers.

-- 
Daniel Jacobowitz
CodeSourcery