* varobj.c (install_new_value): Only call value_get_print_value

[deliverable/binutils-gdb.git] / gdb / dummy-frame.h

diff --git a/gdb/dummy-frame.h b/gdb/dummy-frame.h
index 6d565d1091aac24657bf88c96cd334254eb60425..c0504c716a485f0cae7dc7d95c2ce68386de63aa 100644 (file)
--- a/gdb/dummy-frame.h
+++ b/gdb/dummy-frame.h
@@ -1,6 +1,6 @@
 /* Code dealing with dummy stack frames, for GDB, the GNU debugger.
 
-   Copyright 2002 Free Software Foundation, Inc.
+   Copyright (C) 2002, 2004, 2007 Free Software Foundation, Inc.
 
    This file is part of GDB.
 
@@ -16,8 +16,8 @@
 
    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
-   Foundation, Inc., 59 Temple Place - Suite 330,
-   Boston, MA 02111-1307, USA.  */
+   Foundation, Inc., 51 Franklin Street, Fifth Floor,
+   Boston, MA 02110-1301, USA.  */
 
 #if !defined (DUMMY_FRAME_H)
 #define DUMMY_FRAME_H 1
@@ -27,35 +27,25 @@ struct regcache;
 struct frame_unwind;
 struct frame_id;
 
-/* GENERIC DUMMY FRAMES
-  
-   The following code serves to maintain the dummy stack frames for
-   inferior function calls (ie. when gdb calls into the inferior via
-   call_function_by_hand).  This code saves the machine state before
-   the call in host memory, so we must maintain an independent stack
-   and keep it consistant etc.  I am attempting to make this code
-   generic enough to be used by many targets.
- 
-   The cheapest and most generic way to do CALL_DUMMY on a new target
-   is probably to define CALL_DUMMY to be empty,
-   DEPRECATED_CALL_DUMMY_LENGTH to zero, and CALL_DUMMY_LOCATION to
-   AT_ENTRY.  Then you must remember to define PUSH_RETURN_ADDRESS,
-   because no call instruction will be being executed by the target.
-   Also DEPRECATED_FRAME_CHAIN_VALID as
-   generic_{file,func}_frame_chain_valid and do not set
-   DEPRECATED_FIX_CALL_DUMMY.  */
+/* Push the information needed to identify, and unwind from, a dummy
+   frame onto the dummy frame stack.  */
+
+/* NOTE: cagney/2004-08-02: This interface will eventually need to be
+   parameterized with the caller's thread - that will allow per-thread
+   dummy-frame stacks and, hence, per-thread inferior function
+   calls.  */
+
+/* NOTE: cagney/2004-08-02: In the case of ABIs using push_dummy_code
+   containing more than one instruction, this interface many need to
+   be expanded so that it knowns the lower/upper extent of the dummy
+   frame's code.  */
+
+extern void dummy_frame_push (struct regcache *regcache,
+                             const struct frame_id *dummy_id);
 
 /* If the PC falls in a dummy frame, return a dummy frame
    unwinder.  */
 
-extern const struct frame_unwind *dummy_frame_sniffer (struct frame_info *next_frame);
-
-/* Return the regcache that belongs to the dummy-frame identifed by PC
-   and FP, or NULL if no such frame exists.  */
-/* FIXME: cagney/2002-11-08: The function only exists because of
-   deprecated_generic_get_saved_register.  Eliminate that function and
-   this, to, can go.  */
+extern const struct frame_unwind *const dummy_frame_unwind;
 
-extern struct regcache *deprecated_find_dummy_frame_regcache (CORE_ADDR pc,
-                                                             CORE_ADDR fp);
 #endif /* !defined (DUMMY_FRAME_H)  */