Results of systemtap-20070811 snapshot on i686

[William Cohen]

The main problem on i686 machine is that the tests crash on the
systemtap.stress/current.exp (pr4542), later systemtap.stress,
systemtap.string, and systemtap.syscall tests do not run. The one
other test shown as failed in the log is

FAIL: systemtap.samples/tcptest.stp compilation		pr4901

Manually ran for systemtap.string and found all the tests passed:

runtest --tool_opts install --tool systemtap \
--srcdir /home/wcohen/stap_testing_200708100830/src/testsuite \
systemtap.string/*.exp

No failures for systemtap.string/*.exp

Manually ran for systemtap.syscall:

runtest --tool_opts install --tool systemtap \
--srcdir /home/wcohen/stap_testing_200708100830/src/testsuite \
systemtap.syscall/*.exp

It seems that gcc is getting debuginfo for parameters wrong. Thus, a
number of failures for the systemcall functions.


FAIL: 32-bit access		pr4915
FAIL: 32-bit alarm		pr4915
FAIL: 32-bit chmod		pr4915
FAIL: 32-bit clock		pr4915
FAIL: 32-bit dir		pr4915
FAIL: 32-bit forkwait		pr4915
FAIL: 32-bit futimes		pr4915
FAIL: 32-bit link		pr4915
FAIL: 32-bit mmap		pr4915
FAIL: 32-bit mount		pr4915
FAIL: 32-bit net1		pr4915
FAIL: 32-bit openclose		pr4915
FAIL: 32-bit poll		pr4915
FAIL: 32-bit readwrite		pr4915
FAIL: 32-bit rt_signal		pr4915
FAIL: 32-bit select		pr4915
FAIL: 32-bit signal		pr4915
FAIL: 32-bit stat		pr4915
FAIL: 32-bit statfs		pr4915
FAIL: 32-bit swap		pr4915
FAIL: 32-bit timer		pr4915
FAIL: 32-bit trunc		pr4915
FAIL: 32-bit uid		pr4915
FAIL: 32-bit uid16		pr4915

                 === systemtap Summary ===

# of expected passes            6
# of unexpected failures        24