diff options
| author | Andrew Cagney <cagney@redhat.com> | 2000-02-09 03:28:18 +0000 |
|---|---|---|
| committer | Andrew Cagney <cagney@redhat.com> | 2000-02-09 03:28:18 +0000 |
| commit | 9757ea130216fe7345cff9ad5e82d6c306bd9d8e (patch) | |
| tree | 0ab1eeaf5f2b2c0dc396ed162c22c0c4e55dcecc /gdb/remote.c | |
| parent | 1b0cba4778529d4a3390a76e9a6833a09198d2c7 (diff) | |
| download | gdb-9757ea130216fe7345cff9ad5e82d6c306bd9d8e.tar.gz | |
From JTC: Reduce default remote_timeout to two. Flush defunct code.
Diffstat (limited to 'gdb/remote.c')
| -rw-r--r-- | gdb/remote.c | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/gdb/remote.c b/gdb/remote.c index a99de23198f..90c568c9bc5 100644 --- a/gdb/remote.c +++ b/gdb/remote.c @@ -245,15 +245,6 @@ static struct target_ops remote_async_ops; static struct target_ops extended_async_remote_ops; -/* This was 5 seconds, which is a long time to sit and wait. - Unless this is going though some terminal server or multiplexer or - other form of hairy serial connection, I would think 2 seconds would - be plenty. */ - -/* Changed to allow option to set timeout value. - was static int remote_timeout = 2; */ -extern int remote_timeout; - /* FIXME: cagney/1999-09-23: Even though getpkt was called with ``forever'' still use the normal timeout mechanism. This is currently used by the ASYNC code to guarentee that target reads @@ -5521,13 +5512,6 @@ terminating `#' character and checksum.", &maintenancelist); add_show_from_set - (add_set_cmd ("remotetimeout", no_class, - var_integer, (char *) &remote_timeout, - "Set timeout value for remote read.\n", - &setlist), - &showlist); - - add_show_from_set (add_set_cmd ("remotebreak", no_class, var_boolean, (char *) &remote_break, "Set whether to send break if interrupted.\n", |