From: Daniel Jacobowitz <dan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/testsuite] Reset the timeout duration at the start of each testcase.
Date: Thu, 04 Feb 2010 18:16:00 -0000 [thread overview]
Message-ID: <20100204181621.GB27544@caradoc.them.org> (raw)
In-Reply-To: <20100204174254.GC2715@adacore.com>
On Thu, Feb 04, 2010 at 09:42:54PM +0400, Joel Brobecker wrote:
> Just something that occured to me: What if I changed the implementation
> to just store $timeout at the time gdb.exp is evaluated. From the user's
> perspective, the difference is that he would need to override the value
> of $timeout, which is an already-known variable, instead of setting the
> value of the new default_test_timeout variable. Would that be ugly?
>
> This isn't tested (it's getting late here), but this is what I have
> in mind:
Right, I think this would work fine and I like it.
Here's another trick that will make it less confusing about
initialization order. How about we info exists to set
default_test_timeout from gdb_init, if we haven't yet?
I know I've worked with board files that loaded gdb.exp themselves.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-02-04 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:53 RFC: Fix testsuite timeout clobbers Daniel Jacobowitz
2010-01-29 4:00 ` Joel Brobecker
2010-01-29 15:37 ` Daniel Jacobowitz
2010-02-04 6:08 ` [RFA/testsuite] Reset the timeout duration at the start of each testcase Joel Brobecker
2010-02-04 15:54 ` Tom Tromey
2010-02-04 16:00 ` Daniel Jacobowitz
2010-02-04 17:43 ` Joel Brobecker
2010-02-04 18:16 ` Daniel Jacobowitz [this message]
2010-02-05 7:22 ` Joel Brobecker
2010-02-05 17:33 ` Daniel Jacobowitz
2010-02-08 11:36 ` Joel Brobecker
2010-02-04 6:13 ` RFC: Fix testsuite timeout clobbers Joel Brobecker
2010-01-29 16:49 ` Tom Tromey
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=20100204181621.GB27544@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=brobecker@adacore.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