From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/testsuite] Wait for gdbserver output
Date: Sat, 28 Feb 2004 18:08:00 -0000 [thread overview]
Message-ID: <20040228180841.GA16831@nevyn.them.org> (raw)
In combination with my last change to gdbserver, this provides a nice
improvemet in test runtime. Otherwise we issue "target remote" before the
target issues listen(); that means that we will delay for some suitably long
timeout and retry.
Will commit in a bit.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2004-02-28 Daniel Jacobowitz <drow@mvista.com>
* config/gdbserver.exp (gdbserver_gdb_load): Wait for a complete
line of output.
Index: gdb/testsuite/config/gdbserver.exp
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/gdb/testsuite/config/gdbserver.exp,v
retrieving revision 1.6
diff -u -p -r1.6 gdbserver.exp
--- gdb/testsuite/config/gdbserver.exp 18 Jan 2004 15:23:30 -0000 1.6
+++ gdb/testsuite/config/gdbserver.exp 27 Feb 2004 17:05:13 -0000
@@ -144,11 +144,13 @@ proc gdbserver_gdb_load { server_exec }
"$gdbserver $sockethost$portnum $server_exec"]
}
- # Wait for the server to produce at least one character of output.
+ # Wait for the server to produce at least one line and an additional
+ # character of output. This will wait until any TCP socket has been
+ # created, so that GDB can connect.
expect {
-i $server_spawn_id
-notransfer
- -re . { }
+ -re ".*\n." { }
}
# We can't just call close, because if gdbserver is local then that means
next reply other threads:[~2004-02-28 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 18:08 Daniel Jacobowitz [this message]
2004-02-29 16:52 ` Daniel Jacobowitz
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=20040228180841.GA16831@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/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