|
From: Mark W. <mj...@re...> - 2015-09-12 15:23:50
|
On Sat, 2015-09-12 at 10:06 +0200, Florian Krohm wrote: > On 11.09.2015 17:06, Mark Wielaard wrote: > > > > ppc, kernel-2.6.32, glibc-2.12, gcc-4.4.7, gdb-7.2, binutils-2.20.51.0.2 > > == 587 tests, 7 stderr failures, 0 stdout failures, 0 stderrB failures, > > 0 stdoutB failures, 1 post failure == > > memcheck/tests/leak-segv-jmp (stderr) > > memcheck/tests/linux/stack_changes (stderr) > > memcheck/tests/vbit-test/vbit-test (stderr) > > I'd be interested in the vbit-test failure. This should not happen. Sadly I don't have interactive access to the machine that produces this result and I cannot replicate on a (different) ppc64 setup. Even when running everything under "setarch ppc32" the vbit test passes just fine. All I can offer you at the moment is the unfiltered output: :::::::::::::: memcheck/tests/vbit-test/vbit-test.stderr.out.unfiltered.out :::::::::::::: ==8767== ==8767== Process terminating with default action of signal 4 (SIGILL) ==8767== Illegal opcode at address 0x834D26BC ==8767== at 0x100076F4: valgrind_vex_inject_ir (valgrind.c:85) ==8767== by 0x100076F4: valgrind_execute_test (valgrind.c:111) ==8767== by 0x10001D27: test_binary_op (binary.c:461) ==8767== by 0x10000BCB: main (main.c:135) So it crashed at the VALGRIND_VEX_INJECT_IR for some reason. |