This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [1/3] Remove gdbarch-swapping of remote_address_masked
- From: Jim Blandy <jimb at codesourcery dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 11 Jun 2007 11:03:02 -0700
- Subject: Re: [1/3] Remove gdbarch-swapping of remote_address_masked
- References: <200706082322.l58NMZAD019415@d12av02.megacenter.de.ibm.com>
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
> remote.c contains a gdbarch-swapped variable "remote_address_masked". The
> swap function in fact re-sets the variable to the default address size of
> the target.
>
> This patch attempts to decouple changes to the variable by the user
> (via "set remoteaddresssize") from changes due to architecture switches:
>
> - If the user sets the variable, that value is subsequently used (even
> if the architecture switches).
>
> - If the user never used "set remoteaddresssize" (i.e. the variable
> reads 0), remote_address_masked implicitly uses the current target's
> address size instead.
>
>
> Now this is certainly a change in behaviour, but I'd think the new way
> should actually be more useful ...
>
> Any comments from users of that functionality? Does this make sense?
It seems to me that this makes the remoteaddresssize setting behave
much like language settings: there's 'auto (currently blargh)' and
'blargh'. To be honest, I don't think it's worthwhile making this
variable actually behave that way. I don't even want to know what it
was added for.