aboutsummaryrefslogtreecommitdiff
path: root/gdb/remote.c
diff options
context:
space:
mode:
authorStu Grossman <grossman@cygnus>1994-08-04 17:32:09 +0000
committerStu Grossman <grossman@cygnus>1994-08-04 17:32:09 +0000
commita1e0ba7a1a64ea102542638654a91845393b29f5 (patch)
tree920ac1d91ad373449d07ad576cd56872aa9ddbbf /gdb/remote.c
parent8337ee9d5178460b1a14614666f26edf2bb4d949 (diff)
downloadgdb-a1e0ba7a1a64ea102542638654a91845393b29f5.zip
gdb-a1e0ba7a1a64ea102542638654a91845393b29f5.tar.gz
gdb-a1e0ba7a1a64ea102542638654a91845393b29f5.tar.bz2
* remote.c (remote_open): Set inferior_pid to make kill command
happy. * inflow.c (kill_command): Revert change of Aug 2. Use inferior_pid to determine whether to print out "The program is not being run." message.
Diffstat (limited to 'gdb/remote.c')
-rw-r--r--gdb/remote.c11
1 files changed, 10 insertions, 1 deletions
diff --git a/gdb/remote.c b/gdb/remote.c
index 828b062..a6ea424 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -414,6 +414,15 @@ device is attached to the remote system (e.g. /dev/ttya).");
if (!catch_errors (remote_start_remote, (char *)0,
"Couldn't establish connection to remote target\n", RETURN_MASK_ALL))
pop_target();
+
+ /* Without this, some commands which require an active target (such as kill)
+ won't work. This variable serves (at least) double duty as both the pid
+ of the target process (if it has such), and as a flag indicating that a
+ target is active. These functions should be split out into seperate
+ variables, especially since GDB will someday have a notion of debugging
+ several processes. */
+
+ inferior_pid = -1;
}
/* remote_detach()
@@ -634,7 +643,7 @@ remote_wait (pid, status)
continue;
}
}
- return 0;
+ return inferior_pid;
}
/* Number of bytes of registers this stub implements. */