|
From: Tom H. <to...@co...> - 2005-07-31 15:11:55
|
In message <8701.194.109.230.85.1122813863.squirrel@194.109.230.85>
"Jeroen N. Witmond" <jn...@xs...> wrote:
> > Valgrind-3.0.0 Release Candidate 1 is available from
> > http://www.valgrind.org/downloads/valgrind-3.0.RC1.tar.bz2
> > (md5sum == c3dc8089bebe7aba0822667b7850451e)
>
> On Debian 3.1 (x86), valgrind RC1 works, but shows two unexpected errors
> in the regression test:
>
> * none/tests/x86/int fails with
>
> vex x86->IR: unhandled instruction bytes: 0xCD 0x81 0xC7 0x4
>
> * none/tests/faultstatus fails with
>
> Test 4: PASS
> Test 5: vex x86->IR: unhandled instruction bytes: 0xF 0xB 0x5D 0xC3
> FAIL: expected si_code==2, not 1
> Test 6: vex x86->IR: unhandled instruction bytes: 0xCC 0x5D 0xC3 0x55
> FAIL: expected signal 5, not 4
> Test 7: vex x86->IR: unhandled instruction bytes: 0xCD 0x10 0x5D 0xC3
> FAIL: expected signal 11, not 4
> Test 8: vex x86->IR: unhandled instruction bytes: 0xCE 0x89 0x45 0xFC
> FAIL: expected signal 11, not 4
> Test 9: vex x86->IR: unhandled instruction bytes: 0x62 0x5 0xC 0x90
> FAIL: expected signal 11, not 4
Those tests are testing invalid instructions, but ones which are
supposed to generate a different sort of signal rather than a
basic SIGILL and vex doesn't currently support that as it just
reports an undefined instruction and valgrind then raisess SIGILL.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|