|
From: Rich C. <rc...@wi...> - 2017-05-16 02:57:48
|
valgrind revision: 16379
VEX revision: 3370
C compiler: gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064]
GDB: GNU gdb (GDB; openSUSE 13.2) 7.8
Assembler: GNU assembler (GNU Binutils; openSUSE 13.2) 2.24.0.20140403-6.1
C library: GNU C Library (GNU libc) stable release version 2.19 (git 9a869d822025)
uname -mrs: Linux 3.16.7-29-desktop x86_64
Vendor version: openSUSE 13.2 (Harlequin)
Nightly build on ultra ( gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064] Linux 3.16.7-29-desktop x86_64 )
Started at 2017-05-15 21:30:01 CDT
Ended at 2017-05-15 21:57:39 CDT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 666 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
none/tests/amd64/fb_test_amd64 (stdout)
none/tests/amd64/fb_test_amd64 (stderr)
helgrind/tests/hg05_race2 (stderr)
Last 20 lines of verbose log follow echo
-- Finished tests in exp-sgcheck/tests ---------------------------------
-- Running tests in exp-bbv/tests/amd64-linux -------------------------
clone_test: valgrind --interval-size=100000 --bb-out-file=clone_test.out.bb --pc-out-file=clone_test.out.pc ./clone_test
complex_rep: valgrind --interval-size=100000 --bb-out-file=complex_rep.out.bb ./complex_rep
fldcw_check: valgrind --interval-size=10000 --bb-out-file=fldcw_check.out.bb ./fldcw_check
ll: valgrind --interval-size=1000 --bb-out-file=ll.out.bb ./ll
million: valgrind --interval-size=100000 --bb-out-file=million.out.bb ./million
rep_prefix: valgrind --interval-size=100000 --bb-out-file=rep_prefix.out.bb ./rep_prefix
-- Finished tests in exp-bbv/tests/amd64-linux -------------------------
== 666 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
none/tests/amd64/fb_test_amd64 (stdout)
none/tests/amd64/fb_test_amd64 (stderr)
helgrind/tests/hg05_race2 (stderr)
...checking makefile consistency
...checking header files and include directives
Makefile:1321: recipe for target 'regtest' failed
make: *** [regtest] Error 1
=================================================
./valgrind-new/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2017-05-15 21:44:11.969796194 -0500
+++ hgtls.stdoutB.out 2017-05-15 21:47:04.638024007 -0500
@@ -26,10 +26,10 @@
test static_extern tls_ip 0x........ ip 0x........ equal 1
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test so_local tls_ip 0x........ ip 0x........ equal 1
=================================================
./valgrind-new/helgrind/tests/hg05_race2.stderr.diff
=================================================
--- hg05_race2.stderr.exp 2017-05-15 21:44:15.471699396 -0500
+++ hg05_race2.stderr.out 2017-05-15 21:53:04.185090623 -0500
@@ -26,8 +26,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
----------------------------------------------------------------
@@ -42,8 +41,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/none/tests/amd64/fb_test_amd64.stderr.diff
=================================================
--- fb_test_amd64.stderr.exp 2017-05-15 21:44:17.653639085 -0500
+++ fb_test_amd64.stderr.out 2017-05-15 21:51:23.340876204 -0500
@@ -1,2 +1,26 @@
+vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........
+vex amd64->IR: REX=1 REX.W=1 REX.R=1 REX.X=0 REX.B=1
+vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=0F38
+vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: exec_adcx (fb_test_amd64.h:69)
+ by 0x........: test_adcx (fb_test_amd64.h:166)
+ by 0x........: main (fb_test_amd64.c:1201)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
+
+Process terminating with default action of signal 4 (SIGILL)
+ Illegal opcode at address 0x........
+ at 0x........: exec_adcx (fb_test_amd64.h:69)
+ by 0x........: test_adcx (fb_test_amd64.h:166)
+ by 0x........: main (fb_test_amd64.c:1201)
=================================================
./valgrind-new/none/tests/amd64/fb_test_amd64.stdout.diff
=================================================
--- fb_test_amd64.stdout.exp 2017-05-15 21:44:17.625639859 -0500
+++ fb_test_amd64.stdout.out 2017-05-15 21:51:17.578035399 -0500
@@ -1 +0,0 @@
-final MD5 = 66802c845574c7c69f30d29ef85f7ca3
=================================================
./valgrind-old/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2017-05-15 21:30:25.034669015 -0500
+++ hgtls.stdoutB.out 2017-05-15 21:33:36.905359076 -0500
@@ -26,10 +26,10 @@
test static_extern tls_ip 0x........ ip 0x........ equal 1
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
+test so_extern tls_ip 0x........ ip 0x........ equal 0
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test so_local tls_ip 0x........ ip 0x........ equal 1
=================================================
./valgrind-old/helgrind/tests/hg05_race2.stderr.diff
=================================================
--- hg05_race2.stderr.exp 2017-05-15 21:30:31.618486780 -0500
+++ hg05_race2.stderr.out 2017-05-15 21:39:34.337471978 -0500
@@ -26,8 +26,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
----------------------------------------------------------------
@@ -42,8 +41,7 @@
at 0x........: th (hg05_race2.c:17)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
- Location 0x........ is 0 bytes inside foo.poot[5].plop[11],
- declared at hg05_race2.c:24, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/none/tests/amd64/fb_test_amd64.stderr.diff
=================================================
--- fb_test_amd64.stderr.exp 2017-05-15 21:30:33.005448391 -0500
+++ fb_test_amd64.stderr.out 2017-05-15 21:37:54.054245366 -0500
@@ -1,2 +1,26 @@
+vex amd64->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........ 0x........
+vex amd64->IR: REX=1 REX.W=1 REX.R=1 REX.X=0 REX.B=1
+vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x........ ESC=0F38
+vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: exec_adcx (fb_test_amd64.h:69)
+ by 0x........: test_adcx (fb_test_amd64.h:166)
+ by 0x........: main (fb_test_amd64.c:1201)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
+
+Process terminating with default action of signal 4 (SIGILL)
+ Illegal opcode at address 0x........
+ at 0x........: exec_adcx (fb_test_amd64.h:69)
+ by 0x........: test_adcx (fb_test_amd64.h:166)
+ by 0x........: main (fb_test_amd64.c:1201)
=================================================
./valgrind-old/none/tests/amd64/fb_test_amd64.stdout.diff
=================================================
--- fb_test_amd64.stdout.exp 2017-05-15 21:30:32.976449193 -0500
+++ fb_test_amd64.stdout.out 2017-05-15 21:37:48.296404617 -0500
@@ -1 +0,0 @@
-final MD5 = 66802c845574c7c69f30d29ef85f7ca3
|