> I'll try to investigate, but currently I am all confused, and I
> suspect we have some user-space issues. If only I knew something about ppc...
Sorry for the confusing.
>
> Ananth, could you please confirm once again that step-jump-cont (from
> ptrace-tests testsuite) not fail on your machine? If yes, please tell
> me the version of glibc/gcc. Is PTRACE_GETREGS defined on your
> machine?
Funny enough. The above failure only seen on that particular system so far. In
fact, different PPC64 systems have different results there (roland's git tree +
your lockless patch).
ibm-js20-02.lab.bos.redhat.com
FAIL: watchpoint
ppc-dabr-race: ./../tests/ppc-dabr-race.c:141: handler_fail: Assertion `0'
failed.
/bin/sh: line 5: 16928 Aborted ${dir}$tst
FAIL: ppc-dabr-race
syscall-reset: ./../tests/syscall-reset.c:95: main: Assertion
`(*__errno_location ()) == 38' failed.
errno 14 (Bad address)
unexpected child status 67f
FAIL: syscall-reset
step-fork: ./../tests/step-fork.c:56: handler_fail: Assertion `0' failed.
/bin/sh: line 5: 31144 Aborted ${dir}$tst
FAIL: step-fork
ibm-js22-02.rhts.bos.redhat.com
ibm-js12-04.rhts.bos.redhat.com
ibm-js12-05.rhts.bos.redhat.com
Looks like failed only for syscall-reset and step-fork, as we have discussed
before. I'll be reserving ibm-js20-02.lab.bos.redhat.com at the moment.
Thanks,
CAI Qian
