This is the mail archive of the
mailing list for the GDB project.
Re: Specifying 'async mode' for testing
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