From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: Specifying 'async mode' for testing
Date: Fri, 11 Apr 2008 14:46:00 -0000 [thread overview]
Message-ID: <20080411130304.GA5884@caradoc.them.org> (raw)
In-Reply-To: <ftnn54$ref$1@ger.gmane.org>
On Fri, Apr 11, 2008 at 04:56:04PM +0400, Vladimir Prus wrote:
> Probably. I wonder if it's sensible to assume that GDB, for a given testrun,
> is either in async mode or in sync mode and never switches between those.
> I don't see any value in switching modes on the fly, but maybe I'm missing
> something?
You can tell DejaGNU to test multiple board files in sequence
(runtest --target_board "unix unix/-m32" for instance); so if anything
in a board file can make GDB start with different options, it's
possible.
But I don't think it's important to handle this. Nearly everyone runs
runtest separately per board or runs mostly similar boards like those
above.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-04-11 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 12:14 Vladimir Prus
2008-04-07 19:01 ` Daniel Jacobowitz
2008-04-11 13:03 ` Vladimir Prus
2008-04-11 14:46 ` Daniel Jacobowitz [this message]
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=20080411130304.GA5884@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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