From: Yao Qi <yao@codesourcery.com>
Date: Fri, 14 Sep 2012 00:54:58 +0000 (+0000)
Subject: gdb/
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=d649a38e159d2cb937ba739d84654e7baf44ea71;p=binutils-gdb.git

gdb/
	* valops.c (value_assign): Move observer_notify_target_changed
	below to replace reinit_frame_cache.
---

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 9379601c6b6..b90e81af1af 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2012-09-14  Yao Qi  <yao@codesourcery.com>
+	    Pedro Alves  <palves@redhat.com>
+
+	* valops.c (value_assign): Move observer_notify_target_changed
+	below to replace reinit_frame_cache.
+
 2012-09-13  Khoo Yit Phang  <khooyp@cs.umd.edu>
 
 	Refactor Python "gdb" module into a proper Python package, by
diff --git a/gdb/valops.c b/gdb/valops.c
index 17696eef999..3a5ac0fe8b0 100644
--- a/gdb/valops.c
+++ b/gdb/valops.c
@@ -1374,7 +1374,6 @@ value_assign (struct value *toval, struct value *fromval)
 
 	if (deprecated_register_changed_hook)
 	  deprecated_register_changed_hook (-1);
-	observer_notify_target_changed (&current_target);
 	break;
       }
 
@@ -1396,7 +1395,7 @@ value_assign (struct value *toval, struct value *fromval)
 
   /* Assigning to the stack pointer, frame pointer, and other
      (architecture and calling convention specific) registers may
-     cause the frame cache to be out of date.  Assigning to memory
+     cause the frame cache and regcache to be out of date.  Assigning to memory
      also can.  We just do this on all assignments to registers or
      memory, for simplicity's sake; I doubt the slowdown matters.  */
   switch (VALUE_LVAL (toval))
@@ -1405,7 +1404,7 @@ value_assign (struct value *toval, struct value *fromval)
     case lval_register:
     case lval_computed:
 
-      reinit_frame_cache ();
+      observer_notify_target_changed (&current_target);
 
       /* Having destroyed the frame cache, restore the selected
 	 frame.  */