* Rename remote-es1800.c to remote-es.c

[deliverable/binutils-gdb.git] / gdb / inferior.h

diff --git a/gdb/inferior.h b/gdb/inferior.h
index b6c072447169a71cce5d9ac9bb52d0bcbb4def96..576fcff8b01f8a72e82aa9d9e9c276422f8e271f 100644 (file)
--- a/gdb/inferior.h
+++ b/gdb/inferior.h
@@ -122,6 +122,8 @@ close_exec_file PARAMS ((void));
 extern void
 reopen_exec_file PARAMS ((void));
 
+/* The `resume' routine should only be called in special circumstances.
+   Normally, use `proceed', which handles a lot of bookkeeping.  */
 extern void
 resume PARAMS ((int, int));
 
@@ -151,7 +153,7 @@ terminal_inferior PARAMS ((void));
 extern void
 terminal_init_inferior PARAMS ((void));
 
-/* From infptrace.c or procfs.c */
+/* From infptrace.c */
 
 extern int
 attach PARAMS ((int));
@@ -171,24 +173,15 @@ call_ptrace PARAMS ((int, int, PTRACE_ARG3_TYPE, int));
 
 /* From procfs.c */
 
-#ifdef USE_PROC_FS
-
 extern int
 proc_iterate_over_mappings PARAMS ((int (*) (int, CORE_ADDR)));
 
-extern int
-proc_wait PARAMS ((int *));
-
-extern void
-inferior_proc_init PARAMS ((int));
-
-extern void
-proc_signal_handling_change PARAMS ((void));
+/* From fork-child.c */
 
 extern void
-proc_set_exec_trap PARAMS ((void));
-
-#endif
+fork_inferior PARAMS ((char *, char *, char **,
+                      void (*) (void),
+                      void (*) (int)));
 
 /* From inflow.c */
 
@@ -324,16 +317,27 @@ extern int attach_flag;
 extern CORE_ADDR text_end;
 #define PC_IN_CALL_DUMMY(pc, sp, frame_address) \
   ((pc) >= text_end - CALL_DUMMY_LENGTH         \
-   && (pc) < text_end + DECR_PC_AFTER_BREAK)
+   && (pc) <= text_end + DECR_PC_AFTER_BREAK)
 #else /* Not before text_end.  */
 #if CALL_DUMMY_LOCATION == AFTER_TEXT_END
 extern CORE_ADDR text_end;
 #define PC_IN_CALL_DUMMY(pc, sp, frame_address) \
   ((pc) >= text_end   \
-   && (pc) < text_end + CALL_DUMMY_LENGTH + DECR_PC_AFTER_BREAK)
+   && (pc) <= text_end + CALL_DUMMY_LENGTH + DECR_PC_AFTER_BREAK)
 #else /* On stack.  */
+
+/* This assumes that frame_address is the value of SP_REGNUM before
+   the dummy frame was pushed.  The only known machine for which this
+   isn't true is the 29k, which doesn't use ON_STACK.  Machines for
+   which it isn't true who want to put stack dummies on the stack
+   could provide their own PC_IN_CALL_DUMMY, or perhaps this macro
+   could be re-written to check for the end of the stack instead
+   (using the target_ops->sections).  Are there user programs, libraries,
+   kernel routines, etc. which also execute on the stack?  If so, the
+   latter would be a bad idea.  */
+
 #define PC_IN_CALL_DUMMY(pc, sp, frame_address) \
-  ((sp) INNER_THAN (pc) && (pc) INNER_THAN (frame_address))
+  ((sp) INNER_THAN (pc) && (frame_address != 0) && (pc) INNER_THAN (frame_address))
 #endif /* On stack.  */
 #endif /* Not before text_end.  */
 #endif /* No PC_IN_CALL_DUMMY.  */