Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Jim Blandy <jimb@red-bean.com>,
	Andrew STUBBS <andrew.stubbs@st.com>,
	 gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fixup convenience variables on endian switch
Date: Fri, 18 Nov 2005 01:27:00 -0000	[thread overview]
Message-ID: <8f2776cb0511171153x180b527ya463f6bd17a3e4f4@mail.gmail.com> (raw)
In-Reply-To: <20051117190240.GA19136@nevyn.them.org>

On 11/17/05, Daniel Jacobowitz <drow@false.org> wrote:
> On Thu, Nov 17, 2005 at 10:58:51AM -0800, Jim Blandy wrote:
> > On 11/17/05, Andrew STUBBS <andrew.stubbs@st.com> wrote:
> > > The problem I am actually trying to solve is that we have addresses and
> > > such set up by a script that is sourced before the endian of the target
> > > they will be used with is known.
> >
> > So you only really need to preserve convenience variables whose types
> > are builtin types, and don't go away when symbol tables are reloaded.
> > Wouldn't it be simpler just to have clear_internalvars only clear
> > variables whose types belong to objfiles?
>
> I think you've switched patches - this is about updating variables on
> an endianness switch, not clearing them when we reload.

No, it's popping up a level to figure out how to best address the
original problem.

In light of your stories about losing values, and given Andrew's
description of the troubles that motivated him, I'd agree that simply
always preserving the values of convenience variables that we know how
to preserve is the way to go.


      parent reply	other threads:[~2005-11-17 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 15:13 Andrew STUBBS
2005-11-17  0:34 ` Jim Blandy
2005-11-17  3:57 ` Daniel Jacobowitz
2005-11-17 13:46   ` Andrew STUBBS
2005-11-17 19:22     ` Jim Blandy
2005-11-17 19:25       ` Daniel Jacobowitz
2005-11-17 19:54         ` Andrew STUBBS
2005-11-18  1:27         ` Jim Blandy [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:
  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=8f2776cb0511171153x180b527ya463f6bd17a3e4f4@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.redhat.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