This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa/doco] Test Suite: build != host
[Resending, as it seems like the previous message didn't make it for
some reason.]
> Date: Fri, 20 Aug 2004 11:08:01 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
>
> That's right, it's a literal string.
>
> Here is an excerpt from a gdb.sum file:
>
> Running /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.exp ...
> gdb compile failed, /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c: In function `main':
> /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:39: warning: incompatible implicit declaration of built-in function 'exit'
> /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/unload.c:47: warning: incompatible implicit declaration of built-in function 'exit'
> WARNING: Testcase compile failed, so all tests in this file will automatically fail.
>
> ERROR: (timeout) GDB never initialized after 10 seconds.
> WARNING: remote_expect statement without a default case?!
> ERROR: couldn't load /tmp/migbat-testgdb-49vpUkli/test/gdb.base/unload into gdb (end of file).
> UNRESOLVED: gdb.base/unload.exp: set pending breakpoint
In that case, I suggest to reword the text slightly:
DejaGNU supports separate build, host, and target machines. However,
some @value{GDBN} test scripts do not work if the host machine and
the build machine are not the same. These scripts will say that the
result is ``UNRESOLVED'' in such an environment, like this:
@smallexample
UNRESOLVED: gdb.base/unload.exp: set pending breakpoint
@end smallexample