This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rfa/doco] Test Suite: build != host


andreas> IMHO @samp would be the right one.
eli> It depends on what "UNRESOLVED" means, exactly.  I must confess I
eli> don't understand what does it mean "return UNRESOLVED".  Is it a
eli> literal string printed by the test script, or is it something else?

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
  FAIL: gdb.base/unload.exp: single pending breakpoint info
  FAIL: gdb.base/unload.exp: running program
  FAIL: gdb.base/unload.exp: continuing to end of program
  FAIL: gdb.base/unload.exp: rerun to shared library breakpoint
  FAIL: gdb.base/unload.exp: continuing to end of program second time

This script, unload.exp, has some WARNING, ERROR, UNRESOLVED,
and FAIL results.

(The actual bug has already been fixed, I'm just grabbing this
 excerpt to illustrate UNRESOLVED).

My wording is:

  DejaGNU supports separate build, host, and target machines.  However,
  some @value{GDBN} test scripts do not work if the host machine is
  separate from the build machine.  These scripts will return an
  UNRESOLVED result in such an environment.

I'm open to alternate wording, and I'm definitely open to improving
the markup.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]