testsuite/1647: gdb.base/auxv.exp, incomplete input consumption

[mec dot gnu at mindspring dot com]

>Number:         1647
>Category:       testsuite
>Synopsis:       gdb.base/auxv.exp, incomplete input consumption
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unasigned
>State:          open
>Class:          test-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 14 14:58:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     mec.gnu@mindspring.com
>Release:        gdb HEAD 2004-05-10 00:22:49 UTC
>Organization:
>Environment:
native i686-pc-linux-gnu
tcl 8.4.6, expect 5.41, dejagnu 1.4.4
>Description:
in gdb.base/auxv.exp, proc fetch_auxv, there is a big gdb_test_multiple which does not consume the input up to $gdb_prompt.  This often de-synchronizes and causes a cascade of non-PASS results.

Here is an excerpt from a gdb.log file:

  (gdb) PASS: gdb.base/auxv.exp: continue
  info auxv
  No auxiliary vector found, or failed reading it.FAIL: gdb.base/auxv.exp: info auxv on live process
  gcore /tmp/migbat-testgdb-2jzpc97q/test/gdb.base/auxv.gcore

  (gdb) FAIL: gdb.base/auxv.exp: gcore
  gcore /tmp/migbat-testgdb-2jzpc97q/test/gdb.base/auxv.gcore
  Saved corefile /tmp/migbat-testgdb-2jzpc97q/test/gdb.base/auxv.gcore
  (gdb) FAIL: gdb.base/auxv.exp: continue

The bug happens when the test script stops reading at "No auxiliary vector found".  The script issues the next "gcore" command gets issued before gdb prints the next prompt, and it uses the leftover output from "No auxiliary vector found" to match against that.
>How-To-Repeat:
Run auxv.exp 5-10 times and look at the logs.
>Fix:
Fix fetch_auxv so that it consumes all the input up to the next prompt.
>Release-Note:
>Audit-Trail:
>Unformatted: