|
From: <ma...@bu...> - 2023-02-20 00:34:17
|
valgrind revision: valgrind-3.21.0.GIT-fe008c8739-20230219
C compiler: gcc (GCC) 12.2.1 20220819 (Red Hat 12.2.1-2)
GDB: GNU gdb (GDB) Fedora 12.1-2.fc36
Assembler: GNU assembler version 2.37-36.fc36
C library: GNU C Library (GNU libc) stable release version 2.35.
uname -mrs: Linux 6.0.5-200.fc36.s390x s390x
Vendor version: Fedora Linux 36 (Thirty Six)
Nightly build on lfedora1 ( Fedora release 36 (Thirty Six), s390x )
Started at 2023-02-20 00:00:01 UTC
Ended at 2023-02-20 00:28:02 UTC
Results differ from 24 hours ago
Checking out Valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 794 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
Last 20 lines of verbose log follow echo
syslog: valgrind -q ./syslog
system: valgrind ./system
thread-exits: valgrind ./thread-exits
threaded-fork: valgrind ./threaded-fork
threadederrno: valgrind -q ./threadederrno
timestamp: valgrind --time-stamp=yes ./timestamp
tls: valgrind ./tls
unit_debuglog: valgrind -q ./unit_debuglog
vgprintf: valgrind ./vgprintf
vgprintf_nvalgrind: valgrind ./vgprintf_nvalgrind
-- Finished tests in none/tests ----------------------------------------
== 794 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [Makefile:1431: regtest] Error 1
=================================================
== Results from 24 hours ago ==
=================================================
Checking out Valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 794 tests, 3 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
helgrind/tests/tls_threads (stderr)
drd/tests/pth_mutex_signal (stderr)
Last 20 lines of verbose log follow echo
system: valgrind ./system
thread-exits: valgrind ./thread-exits
threaded-fork: valgrind ./threaded-fork
threadederrno: valgrind -q ./threadederrno
timestamp: valgrind --time-stamp=yes ./timestamp
tls: valgrind ./tls
unit_debuglog: valgrind -q ./unit_debuglog
vgprintf: valgrind ./vgprintf
vgprintf_nvalgrind: valgrind ./vgprintf_nvalgrind
-- Finished tests in none/tests ----------------------------------------
== 794 tests, 3 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
helgrind/tests/tls_threads (stderr)
drd/tests/pth_mutex_signal (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [Makefile:1431: regtest] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2023-02-20 00:14:25.578228888 +0000
--- new.short 2023-02-20 00:28:02.918325296 +0000
***************
*** 8,13 ****
! == 794 tests, 3 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
- helgrind/tests/tls_threads (stderr)
drd/tests/pth_mutex_signal (stderr)
--- 8,12 ----
! == 794 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
***************
*** 16,17 ****
--- 15,17 ----
Last 20 lines of verbose log follow echo
+ syslog: valgrind -q ./syslog
system: valgrind ./system
***************
*** 27,32 ****
! == 794 tests, 3 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
- helgrind/tests/tls_threads (stderr)
drd/tests/pth_mutex_signal (stderr)
--- 27,31 ----
! == 794 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
=================================================
./valgrind-new/drd/tests/pth_mutex_signal.stderr.diff
=================================================
--- pth_mutex_signal.stderr.exp 2023-02-20 00:14:26.108228888 +0000
+++ pth_mutex_signal.stderr.out 2023-02-20 00:24:12.798381070 +0000
@@ -6,10 +6,43 @@
signalling
sleeping
nullHandler running
-unlocking
+Thread 2:
+The impossible happened: mutex is locked simultaneously by two threads: mutex 0x........, recursion count 1, owner 1.
+ at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
+ by 0x........: contender_start (pth_mutex_signal.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: ??? (in /...libc...)
+ by 0x........: ???
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
contender locked mutex
contender unlocking mutex
contender unlocked mutex
+unlocking
+Thread 1:
+Mutex not locked by calling thread: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
joining thread
+Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_join (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
+Destroying locked mutex: mutex 0x........, recursion count 1, owner 0.
+ at 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-02-20 00:14:26.168228888 +0000
+++ hginfo.stderrB.out 2023-02-20 00:16:41.858248888 +0000
@@ -1,5 +1,9 @@
vgdb-error value changed from 0 to 999999
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
@@ -11,6 +15,10 @@
...
Block was alloc'd by thread #x
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
=================================================
./valgrind-new/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2023-02-20 00:14:26.608228888 +0000
+++ vbit-test.stderr.out 2023-02-20 00:20:45.258318894 +0000
@@ -0,0 +1,3 @@
+Conditional jump or move depends on uninitialised value(s)
+ ...
+
=================================================
./valgrind-old/drd/tests/pth_mutex_signal.stderr.diff
=================================================
--- pth_mutex_signal.stderr.exp 2023-02-20 00:00:17.066675523 +0000
+++ pth_mutex_signal.stderr.out 2023-02-20 00:10:39.517315460 +0000
@@ -6,10 +6,43 @@
signalling
sleeping
nullHandler running
-unlocking
+Thread 2:
+The impossible happened: mutex is locked simultaneously by two threads: mutex 0x........, recursion count 1, owner 1.
+ at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
+ by 0x........: contender_start (pth_mutex_signal.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: ??? (in /...libc...)
+ by 0x........: ???
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
contender locked mutex
contender unlocking mutex
contender unlocked mutex
+unlocking
+Thread 1:
+Mutex not locked by calling thread: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
joining thread
+Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_join (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
+Destroying locked mutex: mutex 0x........, recursion count 1, owner 0.
+ at 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-02-20 00:00:17.076675523 +0000
+++ hginfo.stderrB.out 2023-02-20 00:02:59.806715521 +0000
@@ -1,5 +1,9 @@
vgdb-error value changed from 0 to 999999
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
@@ -11,6 +15,10 @@
...
Block was alloc'd by thread #x
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
=================================================
./valgrind-old/helgrind/tests/tls_threads.stderr.diff
=================================================
--- tls_threads.stderr.exp 2023-02-20 00:00:17.096675523 +0000
+++ tls_threads.stderr.out 2023-02-20 00:08:41.426765520 +0000
@@ -1,2 +1,45 @@
starting join in main
-finished join in main
+
+valgrind: m_xarray.c:132 (vgPlain_indexXA): Assertion '(UWord)n < (UWord)xa->usedsizeE' failed.
+
+host stacktrace:
+ ...
+
+sched status:
+ running_tid=4
+
+Thread x: status = VgTs_WaitSys syscall 238 (lwpid 3135546)
+ ...
+ by 0x........: pthread_join_WRK (hg_intercepts.c:...)
+ by 0x........: pthread_join (hg_intercepts.c:...)
+ by 0x........: main (tls_threads.c:94)
+client stack range: [0x........ 0x........] client SP: 0x........
+valgrind stack range: [0x........ 0x........] top usage: 11144 of 1048576
+
+Thread x: status = VgTs_WaitSys syscall 219 (lwpid 3135657)
+ ...
+client stack range: [0x........ 0x........] client SP: 0x........
+valgrind stack range: [0x........ 0x........] top usage: 6928 of 1048576
+
+Thread x: status = VgTs_Runnable (lwpid 3135621)
+ at 0x........: pthread_join_WRK (hg_intercepts.c:...)
+ by 0x........: pthread_join (hg_intercepts.c:...)
+ by 0x........: level1 (tls_threads.c:73)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+client stack range: [0x........ 0x........] client SP: 0x........
+valgrind stack range: [0x........ 0x........] top usage: 6928 of 1048576
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2023-02-20 00:00:17.156675523 +0000
+++ vbit-test.stderr.out 2023-02-20 00:07:08.556745521 +0000
@@ -0,0 +1,3 @@
+Conditional jump or move depends on uninitialised value(s)
+ ...
+
|