Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Cc: Michael Snyder <michsnyd@cisco.com>
Subject: Re: [RFC] mips_abi_update, flush_cached_frames
Date: Sun, 01 May 2005 23:17:00 -0000	[thread overview]
Message-ID: <20050501231655.GA14925@nevyn.them.org> (raw)
In-Reply-To: <20050401010040.GA17642@nevyn.them.org>

On Thu, Mar 31, 2005 at 08:00:40PM -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 31, 2005 at 04:56:05PM -0800, Michael Snyder wrote:
> > Check me out here -- if you change the abi, it seems to me
> > you better make sure you get rid of any cached frames...
> > 
> > 2005-03-31  msnyder  <msnyder@redhat.com>
> > 
> > * mips-tdep.c (mips_abi_update): If abi is changed, cached
> > frames better be flushed.
> 
> Yes and no - I don't think this is the right place to do it.
> My current feeling is that this belongs in
> deprecated_current_gdbarch_select_hack.
> 
> [You're definitely right about the problem, though.  I ran into this on
> ARM last week.]

I've committed this more general fix.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

2005-05-01  Daniel Jacobowitz  <dan@codesourcery.com>

	* gdbarch.sh (deprecated_current_gdbarch_select_hack): Flush
	cached frames when changing gdbarch.
	* gdbarch.c: Regenerated.

Index: gdbarch.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.c,v
retrieving revision 1.323
diff -u -p -r1.323 gdbarch.c
--- gdbarch.c	1 May 2005 19:58:52 -0000	1.323
+++ gdbarch.c	1 May 2005 23:13:39 -0000
@@ -4241,6 +4241,7 @@ deprecated_current_gdbarch_select_hack (
   current_gdbarch_swap_out_hack ();
   current_gdbarch_swap_in_hack (new_gdbarch);
   architecture_changed_event ();
+  flush_cached_frames ();
 }
 
 extern void _initialize_gdbarch (void);
Index: gdbarch.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.sh,v
retrieving revision 1.358
diff -u -p -r1.358 gdbarch.sh
--- gdbarch.sh	1 May 2005 19:58:53 -0000	1.358
+++ gdbarch.sh	1 May 2005 23:13:40 -0000
@@ -2216,6 +2216,7 @@ deprecated_current_gdbarch_select_hack (
   current_gdbarch_swap_out_hack ();
   current_gdbarch_swap_in_hack (new_gdbarch);
   architecture_changed_event ();
+  flush_cached_frames ();
 }
 
 extern void _initialize_gdbarch (void);


  parent reply	other threads:[~2005-05-01 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  0:56 Michael Snyder
2005-04-01  0:59 ` Daniel Jacobowitz
2005-04-01  1:25   ` Michael Snyder
2005-05-01 23:17   ` Daniel Jacobowitz [this message]
2005-05-02 19:23     ` Michael Snyder

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=20050501231655.GA14925@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=michsnyd@cisco.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