2003-05-03 Andrew Cagney <cagney@redhat.com>

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

diff --git a/gdb/dummy-frame.h b/gdb/dummy-frame.h
index bb41e8d7988fae453f286a5b902a95d0b323cffd..3d38cc436cc745f5df0ea79ce063453039565b86 100644 (file)
--- a/gdb/dummy-frame.h
+++ b/gdb/dummy-frame.h
@@ -37,12 +37,13 @@ struct frame_id;
    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, 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
+   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
-   FIX_CALL_DUMMY.  */
+   DEPRECATED_FIX_CALL_DUMMY.  */
 
 /* If the PC falls in a dummy frame, return a dummy frame
    unwinder.  */