summaryrefslogtreecommitdiff
path: root/gdb/inferior.h
diff options
context:
space:
mode:
authorJason Molenda <jsm@bugshack.cygnus.com>1999-07-05 17:58:44 +0000
committerJason Molenda <jsm@bugshack.cygnus.com>1999-07-05 17:58:44 +0000
commit898586e8e8dcfa495ccf88fce9d8a3fe4d3a7625 (patch)
tree1472a0286b800398c881dd858557d7b60aa942e2 /gdb/inferior.h
parent22c86e7f4ad1b5d1172d47119f49a8dbba35f08d (diff)
downloadgdb-898586e8e8dcfa495ccf88fce9d8a3fe4d3a7625.tar.gz
import gdb-1999-07-05 snapshot
Diffstat (limited to 'gdb/inferior.h')
-rw-r--r--gdb/inferior.h13
1 files changed, 13 insertions, 0 deletions
diff --git a/gdb/inferior.h b/gdb/inferior.h
index b87bca9899d..9ba86c7a623 100644
--- a/gdb/inferior.h
+++ b/gdb/inferior.h
@@ -71,6 +71,17 @@ extern char *inferior_io_terminal;
extern int inferior_pid;
+/* Is the inferior running right now, as a result of a 'run&',
+ 'continue&' etc command? This is used in asycn gdb to determine
+ whether a command that the user enters while the target is running
+ is allowed or not. */
+extern int target_executing;
+
+/* Are we simulating synchronous execution? This is used in async gdb
+ to implement the 'run', 'continue' etc commands, which will not
+ redisplay the prompt until the execution is actually over. */
+extern int sync_execution;
+
/* This is only valid when inferior_pid is non-zero.
If this is 0, then exec events should be noticed and responded to
@@ -148,6 +159,8 @@ extern void generic_target_write_fp PARAMS ((CORE_ADDR));
extern void wait_for_inferior PARAMS ((void));
+extern void fetch_inferior_event PARAMS ((void));
+
extern void init_wait_for_inferior PARAMS ((void));
extern void close_exec_file PARAMS ((void));