[patch remote.c] Re-throw connect fail exception

[Andrew Cagney]

Hello,

The attached tweaks remote.c to so that failed connectsion are 
re-propogated back through the caller.

This patch has been lurking in the wings for sometime only no one could 
think of a test-case demonstrating that it fixed a bug.  Today I got 
lucky, compare:


(gdb)
-target-select remote /dev/null
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
&"Couldn't establish connection to remote target\n"
&"Malformed response to offset query, timeout\n"
^connected
(gdb)


with:


(gdb)
-target-select remote /dev/null
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
&"Couldn't establish connection to remote target\n"
&"Malformed response to offset query, timeout\n"
^error,msg="Malformed response to offset query, timeout"
(gdb)


The fix is in.

So, how legitimate is it do do something like:

(gdb) target remote /dev/null

as part of a test case?

Andrew
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diffs
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20020519/b89d4214/attachment.ksh>