This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Use of lval_register?
On Thu, Jun 05, 2003 at 01:48:45PM -0400, Andrew Cagney wrote:
>
> >>>I think it should update the cached copy. I'm not so sure it should
> >>>update the in-memory copy, if the var has moved. That would require
> >>>re-evaluating the expression that produced $1 wouldn't it?
> >
> >>
> >>Eventually. For the moment I'm just worred about getting it to
> >>re-evaluate the registers the value is assumed to reside in.
> >>
> >>Or should it only modify the history pool (modifying memory is weird
> >>here, but where to draw the line is also weird).
> >
> >
> >After some more thought, I suppose it should modify both the pool and
> >memory. It's just not clear how to find out where in memory it should
> >be, now...
>
> Or just modify the pool?
I'd be pretty surprised by this behavior. I sometimes use values this
way, to tweak a member of a struct later. If we're only going to
change the copy in the pool then I suspect we should refuse to allow
changes at all, if we can't change the program's copy.
> varobj provides a mechanism for modifying / tracking values in the target.
Hmm.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer