From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: allow gdb_test_multiple { -timeout n }
Date: Fri, 12 Mar 2010 21:09:00 -0000 [thread overview]
Message-ID: <201003122109.02279.pedro@codesourcery.com> (raw)
I've applied this patch of Daniel's. It tweaks gdb_test_multiple
to be able to forward expect a -timeout switch. E.g.,
instead of:
set prev_timeout $timeout
set timeout 10
gdb_test_multiple "" "" {
-re "$gdb_prompt $" { }
}
set timeout $prev_timeout
you can simply do:
gdb_test_multiple "" "" {
-timeout 10
-re "$gdb_prompt $" { }
}
--
Pedro Alves
next reply other threads:[~2010-03-12 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 21:09 Pedro Alves [this message]
2010-03-12 21:11 ` Pedro Alves
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=201003122109.02279.pedro@codesourcery.com \
--to=pedro@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