Hi,
On Thu, 24 Jul 2008 08:38:16 +0200, Wenji Huang wrote:
> [tests]$ ./x86_64-cs
> ./x86_64-cs: WIFSTOPPED - WSTOPSIG = 4
> x86_64-cs: x86_64-cs.c:160: main: Assertion `0' failed.
Thanks, committed (and also that unexpected values are a PASS now - a problem
would be just a kernel crash).
Regar
Yeah, that test case was a regression test for a bug that only existed on
x86-64 (for 32-bit processes), hence the name. The i386 kernel gives
SIGILL for the "can't iret" failure though it gives SIGSEGV for a real GPF.
It should be made consistent upstream. But just change the test case
to accept
Hi,
The test case x86_64-cs will fail in utrace-patched kernel(2.6.26/x86),
also vanilla kernel.
[tests]$ ./x86_64-cs
./x86_64-cs: WIFSTOPPED - WSTOPSIG = 4
x86_64-cs: x86_64-cs.c:160: main: Assertion `0' failed.
Aborted
Related piece of the testcase:
# ifdef __i386__
/* Resuming with
