Specifying 'async mode' for testing

Specifying 'async mode' for testing

[Vladimir Prus]

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?

Thanks,
Volodya

Re: Specifying 'async mode' for testing

[Daniel Jacobowitz]

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

Re: Specifying 'async mode' for testing

[Vladimir Prus]

Daniel Jacobowitz wrote:

> 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?

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?

- Volodya

Re: Specifying 'async mode' for testing

[Daniel Jacobowitz]

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