[RFA/testsuite] Workaround timeout in default.exp

[Joel Brobecker <brobecker@gnat.com>]

This is a problem that has been bugging me on AIX for as long as I can
remember: default.exp on AIX was taking hours to complete. So far, I've
just worked-around the problem by deactivating this test on that
platform, always postponing the task of looking at the source of the
problem for later.

Turns out we have two commands that have the gdb prompt in their
output, and this is somehow confusing test_gdb and test_gdb_multiple
into a timeout. I couldn't understand exactly why this was happening
for lack of time. I'm wondering if this might be an expect or dejagnu
bug, as it works fine on x86-linux for instance...

The attached patch works-around the problem by using the send_gdb and
gdb_expect pair instead of test_gdb. This short-circuits the smart
machinery behind test_gdb, and allows runtest to match the output
from the 2 commands correctly. With this patch, the testscase completes
successfully within a reasonable amount of time.

I added some comments explaining what was happening with test_gdb and
why we use send_gdb and gdb_expect instead, to make it clear why I made
this change.

2004-05-18  J. Brobecker  <brobecker@gnat.com>

	* gdb.base/default.exp: Rewrite a couple of tests to work-around
	a problem that causes this test and all the following tests to
	timeout.

Tested on AIX 5.1 and x86-linux. Would that be OK to apply?

-- 
Joel
Attachment:
default.exp.diff
Description: Text document