aboutsummaryrefslogtreecommitdiff
path: root/gdb/remote.c
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1991-04-24 17:14:10 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1991-04-24 17:14:10 +0000
commiteb7ba50c7c0df092fdad830275b2d4c74c35e0ac (patch)
tree9f524bcfae9ba586476de7489a7ebbd9ab32eedc /gdb/remote.c
parent2403f49b376fd88066b676e92c95ca6f012f0e61 (diff)
downloadgdb-eb7ba50c7c0df092fdad830275b2d4c74c35e0ac.zip
gdb-eb7ba50c7c0df092fdad830275b2d4c74c35e0ac.tar.gz
gdb-eb7ba50c7c0df092fdad830275b2d4c74c35e0ac.tar.bz2
* remote.c (getpkt): Don't set immediate_quit.
Diffstat (limited to 'gdb/remote.c')
-rw-r--r--gdb/remote.c14
1 files changed, 14 insertions, 0 deletions
diff --git a/gdb/remote.c b/gdb/remote.c
index c5673d2..d3df38d 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -615,8 +615,20 @@ getpkt (buf)
int c;
unsigned char c1, c2;
+#if 0
+ /* Sorry, this will cause all hell to break loose, i.e. we'll end
+ up in the command loop with an inferior, but (at least if this
+ happens in remote_wait or some such place) without a current_frame,
+ having set up prev_* in wait_for_inferior, etc.
+
+ If it is necessary to have such an "emergency exit", seems like
+ the only plausible thing to do is to say the inferior died, and
+ make the user reattach if they want to. Perhaps with a prompt
+ asking for confirmation. */
+
/* allow immediate quit while reading from device, it could be hung */
immediate_quit++;
+#endif /* 0 */
while (1)
{
@@ -645,7 +657,9 @@ getpkt (buf)
write (remote_desc, "-", 1);
}
+#if 0
immediate_quit--;
+#endif
write (remote_desc, "+", 1);