Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [1/3] Remove gdbarch-swapping of remote_address_masked
Date: Mon, 11 Jun 2007 18:03:00 -0000	[thread overview]
Message-ID: <m34plejrmx.fsf@codesourcery.com> (raw)
In-Reply-To: <200706082322.l58NMZAD019415@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Sat, 9 Jun 2007 01:22:35 +0200 (CEST)")


"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.


  reply	other threads:[~2007-06-11 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 23:22 Ulrich Weigand
2007-06-11 18:03 ` Jim Blandy [this message]
2007-06-12 16:14   ` Ulrich Weigand
2007-06-12 15:34 ` Daniel Jacobowitz
2007-06-13 19:01 ` Joel Brobecker
2007-06-14 13:04   ` Ulrich Weigand
2007-06-22 12:52 ` Ulrich Weigand

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=m34plejrmx.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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