Re: New fhpd commands: ptype & plocation

[Phil Muldoon <pmuldoon at redhat dot com>]

Andrew Cagney wrote:
> Phil Muldoon wrote:
> > Apart from the output code, and parsing code in fhpd, is the "get the 
> > location" code placed in a utility class somewhere? Can you give a 
> > programming example of given variable foo, how to get a location or 
> > locations in memory of where it resides?
> Phil,
>
> I wouldn't become too attached to this command's implementation as it 
> currently stands; rather just view it as a a glimpse of what is to 
> come.  That command reports the expression's result's location which 
> isn't sufficient; instead a walk of the expression tree that generates 
> a list of all referenced locations is going to be needed.
>
> I would define the frysk.proc. object interface that you require and 
> expect the location tree walk code to generate that that information; 
> rather than try to have frysk.proc directly access frysk.debuginfo.

That's fair enough. From the observer point of view, all that is needed 
is a memory location and range -  at the first pass. Later on as debug 
register usage is optimized to not map duplicate/overlapping ranges, it 
might be more meta-data.

Still all of the above (Teresa's work) is neat stuff indeed. Happy to 
see it in the repo.

Regards

Phil