From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: RFA: Recognize 'unknown host' errors when connecting to gdbserver
Date: Thu, 20 Dec 2007 22:03:00 -0000 [thread overview]
Message-ID: <m3fxxx8662.fsf@codesourcery.com> (raw)
This patch makes the GDB test suite not hang when trying to connect to
gdbserver. Granted, looking up 'localhost' shouldn't give an error;
why that happens on my machine is a separate question.
gdb/testsuite/ChangeLog:
2007-12-20 Jim Blandy <jimb@codesourcery.com>
* lib/gdbserver-support.exp (gdb_target_cmd): Recognize 'unknown
host' errors.
* lib/mi-support.exp (mi_gdb_target_cmd): Same.
diff -r 69e7c25fdf59 gdb/testsuite/lib/gdbserver-support.exp
--- a/gdb/testsuite/lib/gdbserver-support.exp Wed Dec 19 14:27:19 2007 -0800
+++ b/gdb/testsuite/lib/gdbserver-support.exp Thu Dec 20 11:14:56 2007 -0800
@@ -52,6 +52,9 @@ proc gdb_target_cmd { targetname serialp
send_gdb "y\n"
exp_continue
}
+ -re "unknown host.*$gdb_prompt" {
+ verbose "Couldn't look up $serialport"
+ }
-re "Couldn't establish connection to remote.*$gdb_prompt $" {
verbose "Connection failed"
}
diff -r 69e7c25fdf59 gdb/testsuite/lib/mi-support.exp
--- a/gdb/testsuite/lib/mi-support.exp Wed Dec 19 14:27:19 2007 -0800
+++ b/gdb/testsuite/lib/mi-support.exp Thu Dec 20 11:14:56 2007 -0800
@@ -332,6 +332,9 @@ proc mi_gdb_target_cmd { targetname seri
verbose "Set target to $targetname";
return 0;
}
+ -re "unknown host.*$mi_gdb_prompt" {
+ verbose "Couldn't look up $serialport"
+ }
-re "Couldn't establish connection to remote.*$mi_gdb_prompt$" {
verbose "Connection failed";
}
next reply other threads:[~2007-12-20 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 22:03 Jim Blandy [this message]
2008-01-29 17:08 ` Daniel Jacobowitz
2008-01-29 19:55 ` Jim Blandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fxxx8662.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox