From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: Specifying 'async mode' for testing
Date: Mon, 07 Apr 2008 19:01:00 -0000 [thread overview]
Message-ID: <20080407121344.GA6675@caradoc.them.org> (raw)
In-Reply-To: <200804071246.56722.vladimir@codesourcery.com>
On Mon, Apr 07, 2008 at 12:46:56PM +0400, Vladimir Prus wrote:
>
> While updating MI testsuite for async mode and other discussed changes,
> I find it preferable to know if we're testing async-enabled target, or
> not. In particular, because in async mode the order of some output is
> different, and creating a regexp that will catch all valid output and
> will not miss invalid output is a bit complex.
>
> What's the best way to specify async mode? One approach is use a board
> file, and put:
>
> set_board_info async 1
>
> there, but creating board file is a nuisance. Is there any way to specify
> async mode on the command line of runtest?
You could ask GDB whether it was in async mode, with show? Or you
could use "runtest GDB_ASYNC=1", then it will show up as a TCL global.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-07 12:14 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 [this message]
2008-04-11 13:03 ` Vladimir Prus
2008-04-11 14:46 ` 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=20080407121344.GA6675@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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