Re: [rfc][23/37] Eliminate builtin_type_ macros: Platform-neutral types for internal variables

Daniel Jacobowitz
2008-09-02T22:00:32Z

On Tue, Sep 02, 2008 at 11:54:15PM +0200, Ulrich Weigand wrote:
> I guess that would mean current_gdbarch for now. However, I had been
> wondering what that means for the multi-architecture case -- if you
> set $_ in one frame, and then switch to a frame using a different
> architecture and use $_ as inferior call argument there, we'll still
> get pointers the architecture doesn't understand ...

Yes indeed. But this problem's not specific to $_; you could get it
by calling a function from the other architecture or using a variable
from the history.

--
Daniel Jacobowitz
CodeSourcery