This is the mail archive of the
mailing list for the GDB project.
Re: Specifying 'async mode' for testing
- From: Daniel Jacobowitz <drow at false dot org>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 7 Apr 2008 08:13:44 -0400
- Subject: Re: Specifying 'async mode' for testing
- References: <firstname.lastname@example.org>
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.