public inbox for
 help / color / mirror / Atom feed
From: Phil Muldoon <>
To: Andrew Cagney <>
Cc: Teresa Thomas <>, frysk <>
Subject: Re: New fhpd commands: ptype & plocation
Date: Thu, 27 Sep 2007 14:53:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.



      reply	other threads:[~2007-09-27 14:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 20:43 Teresa Thomas
2007-09-27  6:49 ` Phil Muldoon
2007-09-27 14:14   ` Teresa Thomas
2007-09-27 14:21     ` Phil Muldoon
2007-09-27 14:47   ` Andrew Cagney
2007-09-27 14:53     ` Phil Muldoon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).