diff options
author | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-06-09 00:41:06 +0000 |
---|---|---|
committer | Jim Kingdon <jkingdon@engr.sgi.com> | 1993-06-09 00:41:06 +0000 |
commit | bf3b8abd19272a3942e5d64552f6068d98d255fc (patch) | |
tree | 749063c1307abdeaf1edce87f2307681a590d6d4 /gdb | |
parent | 7f4bf88f6c6807db13c318d779b8b114dd37bf79 (diff) | |
download | gdb-bf3b8abd19272a3942e5d64552f6068d98d255fc.zip gdb-bf3b8abd19272a3942e5d64552f6068d98d255fc.tar.gz gdb-bf3b8abd19272a3942e5d64552f6068d98d255fc.tar.bz2 |
add comment
Diffstat (limited to 'gdb')
-rw-r--r-- | gdb/serial.c | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/gdb/serial.c b/gdb/serial.c index e5ccf1d..0e5a064 100644 --- a/gdb/serial.c +++ b/gdb/serial.c @@ -122,6 +122,21 @@ serial_close(scb) } #if 0 +/* +The connect command is #if 0 because I hadn't thought of an elegant +way to wait for I/O on two serial_t's simultaneously. Two solutions +came to mind: + + 1) Fork, and have have one fork handle the to user direction, + and have the other hand the to target direction. This + obviously won't cut it for MSDOS. + + 2) Use something like select. This assumes that stdin and + the target side can both be waited on via the same + mechanism. This may not be true for DOS, if GDB is + talking to the target via a TCP socket. +-grossman, 8 Jun 93 +*/ /* Connect the user directly to the remote system. This command acts just like the 'cu' or 'tip' command. Use <CR>~. or <CR>~^D to break out. */ |