diff options
| -rw-r--r-- | gdb/ChangeLog | 2 | ||||
| -rw-r--r-- | gdb/remote.c | 14 |
2 files changed, 16 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 9dbf8e4..e2a88f1 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,7 @@ Wed Apr 24 09:45:17 1991 Jim Kingdon (kingdon at cygint.cygnus.com) + * remote.c (getpkt): Don't set immediate_quit. + * blockframe.c, frame.h (reinit_frame_cache): New function. solib.c (solib_add), symfile.c ({,add_}symbol_file_command): Use it. 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); |