|
From: <ma...@gc...> - 2023-01-09 10:31:43
|
valgrind revision: valgrind-3.21.0.GIT-d320fc123b-20230108
C compiler: gcc (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.4) 4.8.4
GDB: GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
Assembler: GNU assembler (GNU Binutils for Ubuntu) 2.24
C library: GNU C Library (Ubuntu EGLIBC 2.19-0ubuntu6.15) stable release version 2.19
uname -mrs: Linux 3.13.0-170-generic aarch64
Vendor version: Ubuntu 14.04.6 LTS, Trusty Tahr
Nightly build on gcc114-arm64 ( Ubuntu 14.04 trusty aarch64 )
Started at 2023-01-09 00:00:01 PST
Ended at 2023-01-09 02:31:29 PST
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
== 648 tests, 20 stderr failures, 4 stdout failures, 13 stderrB failures, 16 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stdoutB)
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/hgtls (stdoutB)
gdbserver_tests/mcblocklistsearch (stderrB)
gdbserver_tests/mcbreak (stdoutB)
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stdoutB)
gdbserver_tests/mcclean_after_fork (stderrB)
gdbserver_tests/mcinfcallWSRU (stderrB)
gdbserver_tests/mcleak (stdoutB)
gdbserver_tests/mcleak (stderrB)
gdbserver_tests/mcmain_pic (stdoutB)
gdbserver_tests/mcmain_pic (stderrB)
gdbserver_tests/mcsignopass (stdoutB)
gdbserver_tests/mcsigpass (stdoutB)
gdbserver_tests/mcvabits (stdoutB)
gdbserver_tests/mcvabits (stderrB)
gdbserver_tests/mcwatchpoints (stdoutB)
gdbserver_tests/mssnapshot (stdoutB)
gdbserver_tests/mssnapshot (stderrB)
gdbserver_tests/nlcontrolc (stdoutB)
gdbserver_tests/nlgone_abrt (stdoutB)
gdbserver_tests/nlgone_abrt (stderrB)
gdbserver_tests/nlgone_exit (stderrB)
gdbserver_tests/nlgone_return (stdoutB)
gdbserver_tests/nlgone_return (stderrB)
gdbserver_tests/nlpasssigalrm (stdoutB)
gdbserver_tests/nlpasssigalrm (stderrB)
gdbserver_tests/nlvgdbsigqueue (stdoutB)
memcheck/tests/dw4 (stderr)
memcheck/tests/sigaltstack (stderr)
memcheck/tests/supp_unknown (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/varinforestrict (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc20_verifywrap (stderr)
drd/tests/pth_mutex_signal (stderr)
drd/tests/std_mutex (stderr)
drd/tests/tc04_free_lock (stderr)
drd/tests/tc09_bad_unlock (stderr)
drd/tests/timed_mutex (stderr)
none/tests/bigcode (stdout)
none/tests/bigcode (stderr)
none/tests/map_unmap (stdout)
none/tests/map_unmap (stderr)
none/tests/sigstackgrowth (stdout)
none/tests/sigstackgrowth (stderr)
none/tests/stackgrowth (stdout)
none/tests/stackgrowth (stderr)
Last 20 lines of verbose log follow echo
memcheck/tests/varinforestrict (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc20_verifywrap (stderr)
drd/tests/pth_mutex_signal (stderr)
drd/tests/std_mutex (stderr)
drd/tests/tc04_free_lock (stderr)
drd/tests/tc09_bad_unlock (stderr)
drd/tests/timed_mutex (stderr)
none/tests/bigcode (stdout)
none/tests/bigcode (stderr)
none/tests/map_unmap (stdout)
none/tests/map_unmap (stderr)
none/tests/sigstackgrowth (stdout)
none/tests/sigstackgrowth (stderr)
none/tests/stackgrowth (stdout)
none/tests/stackgrowth (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [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
== 648 tests, 20 stderr failures, 4 stdout failures, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/hgtls (stdoutB)
memcheck/tests/dw4 (stderr)
memcheck/tests/sigaltstack (stderr)
memcheck/tests/supp_unknown (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/varinforestrict (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc20_verifywrap (stderr)
drd/tests/pth_mutex_signal (stderr)
drd/tests/std_mutex (stderr)
drd/tests/tc04_free_lock (stderr)
drd/tests/tc09_bad_unlock (stderr)
drd/tests/timed_mutex (stderr)
none/tests/bigcode (stdout)
none/tests/bigcode (stderr)
none/tests/map_unmap (stdout)
none/tests/map_unmap (stderr)
none/tests/sigstackgrowth (stdout)
none/tests/sigstackgrowth (stderr)
none/tests/stackgrowth (stdout)
none/tests/stackgrowth (stderr)
Last 20 lines of verbose log follow echo
memcheck/tests/varinforestrict (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc20_verifywrap (stderr)
drd/tests/pth_mutex_signal (stderr)
drd/tests/std_mutex (stderr)
drd/tests/tc04_free_lock (stderr)
drd/tests/tc09_bad_unlock (stderr)
drd/tests/timed_mutex (stderr)
none/tests/bigcode (stdout)
none/tests/bigcode (stderr)
none/tests/map_unmap (stdout)
none/tests/map_unmap (stderr)
none/tests/sigstackgrowth (stdout)
none/tests/sigstackgrowth (stderr)
none/tests/stackgrowth (stdout)
none/tests/stackgrowth (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [regtest] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2023-01-09 00:28:08.640539909 -0800
--- new.short 2023-01-09 00:55:38.972523152 -0800
***************
*** 8,12 ****
! == 648 tests, 20 stderr failures, 4 stdout failures, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/hgtls (stdoutB)
memcheck/tests/dw4 (stderr)
--- 8,39 ----
! == 648 tests, 20 stderr failures, 4 stdout failures, 13 stderrB failures, 16 stdoutB failures, 0 post failures ==
! gdbserver_tests/hginfo (stdoutB)
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/hgtls (stdoutB)
+ gdbserver_tests/mcblocklistsearch (stderrB)
+ gdbserver_tests/mcbreak (stdoutB)
+ gdbserver_tests/mcbreak (stderrB)
+ gdbserver_tests/mcclean_after_fork (stdoutB)
+ gdbserver_tests/mcclean_after_fork (stderrB)
+ gdbserver_tests/mcinfcallWSRU (stderrB)
+ gdbserver_tests/mcleak (stdoutB)
+ gdbserver_tests/mcleak (stderrB)
+ gdbserver_tests/mcmain_pic (stdoutB)
+ gdbserver_tests/mcmain_pic (stderrB)
+ gdbserver_tests/mcsignopass (stdoutB)
+ gdbserver_tests/mcsigpass (stdoutB)
+ gdbserver_tests/mcvabits (stdoutB)
+ gdbserver_tests/mcvabits (stderrB)
+ gdbserver_tests/mcwatchpoints (stdoutB)
+ gdbserver_tests/mssnapshot (stdoutB)
+ gdbserver_tests/mssnapshot (stderrB)
+ gdbserver_tests/nlcontrolc (stdoutB)
+ gdbserver_tests/nlgone_abrt (stdoutB)
+ gdbserver_tests/nlgone_abrt (stderrB)
+ gdbserver_tests/nlgone_exit (stderrB)
+ gdbserver_tests/nlgone_return (stdoutB)
+ gdbserver_tests/nlgone_return (stderrB)
+ gdbserver_tests/nlpasssigalrm (stdoutB)
+ gdbserver_tests/nlpasssigalrm (stderrB)
+ gdbserver_tests/nlvgdbsigqueue (stdoutB)
memcheck/tests/dw4 (stderr)
--tools=none,memcheck,callgrind,helgrind,cachegrind,drd,massif --reps=3 --vg=../valgrind-new --vg=../valgrind-old
-- Running tests in perf ----------------------------------------------
-- bigcode1 --
bigcode1 valgrind-new:0.20s no: 3.6s (17.9x, -----) me: 7.9s (39.4x, -----) ca:35.4s (177.1x, -----) he: 4.2s (21.0x, -----) ca: 9.5s (47.5x, -----) dr: 4.1s (20.4x, -----) ma: 4.3s (21.7x, -----)
bigcode1 valgrind-old:0.20s no: 3.6s (17.9x, 0.0%) me: 7.9s (39.4x, 0.0%) ca:35.4s (176.9x, 0.1%) he: 4.2s (21.0x, 0.2%) ca: 9.5s (47.4x, 0.3%) dr: 4.2s (20.9x, -2.5%) ma: 4.3s (21.7x, 0.0%)
-- bigcode2 --
bigcode2 valgrind-new:0.21s no: 9.2s (43.7x, -----) me:18.6s (88.5x, -----) ca:66.9s (318.5x, -----) he:10.8s (51.7x, -----) ca:16.6s (79.1x, -----) dr:10.4s (49.3x, -----) ma:10.5s (50.1x, -----)
bigcode2 valgrind-old:0.21s no: 9.2s (43.9x, -0.4%) me:18.5s (88.1x, 0.4%) ca:67.0s (318.9x, -0.1%) he:10.8s (51.6x, 0.2%) ca:16.6s (79.2x, -0.1%) dr:10.3s (49.1x, 0.5%) ma:10.5s (50.0x, 0.4%)
-- bz2 --
bz2 valgrind-new:1.12s no: 3.9s ( 3.5x, -----) me:14.3s (12.7x, -----) ca:40.3s (36.0x, -----) he:20.2s (18.0x, -----) ca:30.9s (27.6x, -----) dr:29.4s (26.3x, -----) ma: 4.2s ( 3.8x, -----)
bz2 valgrind-old:1.12s no: 3.9s ( 3.5x, 0.0%) me:14.2s (12.7x, 0.1%) ca:40.3s (36.0x, 0.0%) he:20.2s (18.0x, -0.1%) ca:30.6s (27.3x, 0.9%) dr:29.5s (26.3x, -0.1%) ma: 4.2s ( 3.7x, 0.7%)
-- fbench --
fbench valgrind-new:0.54s no: 4.0s ( 7.4x, -----) me: 8.1s (14.9x, -----) ca:16.9s (31.3x, -----) he: 7.0s (12.9x, -----) ca:10.2s (18.9x, -----) dr: 8.5s (15.8x, -----) ma: 4.3s ( 8.0x, -----)
fbench valgrind-old:0.54s no: 4.0s ( 7.3x, 0.5%) me: 8.1s (15.0x, -0.5%) ca:16.9s (31.3x, 0.1%) he: 6.9s (12.8x, 0.4%) ca:10.2s (18.9x, 0.1%) dr: 8.6s (15.9x, -0.4%) ma: 4.3s ( 7.9x, 0.7%)
-- ffbench --
ffbench valgrind-new:0.53s no: 2.9s ( 5.5x, -----) me: 5.8s (10.9x, -----) ca: 5.9s (11.1x, -----) he:16.9s (31.9x, -----) ca:11.2s (21.1x, -----) dr: 9.9s (18.8x, -----) ma: 3.1s ( 5.9x, -----)
ffbench valgrind-old:0.53s no: 2.9s ( 5.4x, 1.0%) me: 5.8s (10.9x, -0.2%) ca: 5.9s (11.1x, 0.0%) he:16.9s (31.8x, 0.3%) ca:11.2s (21.1x, 0.2%) dr:10.0s (18.8x, -0.4%) ma: 3.1s ( 5.8x, 0.6%)
-- heap --
heap valgrind-new:0.52s no: 2.6s ( 5.0x, -----) me:11.1s (21.3x, -----) ca:23.2s (44.6x, -----) he:16.8s (32.3x, -----) ca:13.0s (25.0x, -----) dr:10.2s (19.7x, -----) ma: 6.0s (11.5x, -----)
heap valgrind-old:0.52s no: 2.7s ( 5.1x, -1.5%) me:11.2s (21.5x, -0.5%) ca:23.1s (44.5x, 0.3%) he:16.7s (32.1x, 0.4%) ca:13.0s (25.1x, -0.1%) dr:10.3s (19.8x, -0.3%) ma: 6.0s (11.5x, -0.7%)
-- heap_pdb4 --
heap_pdb4 valgrind-new:0.57s no: 2.8s ( 5.0x, -----) me:17.9s (31.3x, -----) ca:25.2s (44.2x, -----) he:18.8s (32.9x, -----) ca:14.9s (26.1x, -----) dr:11.6s (20.4x, -----) ma: 6.3s (11.0x, -----)
heap_pdb4 valgrind-old:0.57s no: 2.8s ( 5.0x, 0.0%) me:18.3s (32.1x, -2.4%) ca:24.5s (42.9x, 2.8%) he:18.7s (32.9x, 0.2%) ca:14.9s (26.1x, 0.0%) dr:11.6s (20.4x, 0.3%) ma: 6.2s (11.0x, 0.2%)
-- many-loss-records --
many-loss-records valgrind-new:0.07s no: 0.7s ( 9.3x, -----) me: 3.2s (45.3x, -----) ca: 3.4s (48.3x, -----) he: 2.7s (38.6x, -----) ca: 2.7s (38.4x, -----) dr: 2.4s (34.6x, -----) ma: 1.6s (23.4x, -----)
many-loss-records valgrind-old:0.07s no: 0.6s ( 9.0x, 3.1%) me: 3.1s (44.7x, 1.3%) ca: 3.4s (48.3x, 0.0%) he: 2.9s (41.0x, -6.3%) ca: 2.4s (34.1x, 11.2%) dr: 2.4s (34.7x, -0.4%) ma: 1.8s (25.0x, -6.7%)
-- many-xpts --
many-xpts valgrind-new:0.12s no: 0.9s ( 7.3x, -----) me: 3.4s (28.3x, -----) ca: 8.2s (68.6x, -----) he: 4.5s (37.3x, -----) ca: 3.6s (29.8x, -----) dr: 3.6s (29.8x, -----) ma: 3.7s (30.7x, -----)
many-xpts valgrind-old:0.12s no: 0.8s ( 7.1x, 3.4%) me: 3.5s (28.8x, -1.5%) ca: 8.2s (68.3x, 0.4%) he: 4.7s (39.0x, -4.5%) ca: 3.6s (29.7x, 0.6%) dr: 3.6s (30.0x, -0.6%) ma: 3.5s (29.6x, 3.5%)
-- memrw --
memrw valgrind-new:0.28s no: 1.1s ( 4.0x, -----) me: 2.7s ( 9.7x, -----) ca: 8.7s (30.9x, -----) he:15.4s (55.0x, -----) ca: 4.2s (15.0x, -----) dr: 3.1s (11.0x, -----) ma: 1.4s ( 5.2x, -----)
memrw valgrind-old:0.28s no: 1.1s ( 3.9x, 1.8%) me: 2.7s ( 9.6x, 1.8%) ca: 8.7s (30.9x, 0.0%) he:15.6s (55.5x, -1.0%) ca: 4.2s (15.0x, 0.0%) dr: 3.1s (11.2x, -2.3%) ma: 1.4s ( 5.1x, 1.4%)
-- sarp --
sarp valgrind-new:0.03s no: 0.6s (18.3x, -----) me: 3.9s (128.7x, -----) ca: 4.7s (156.7x, -----) he:10.7s (355.0x, -----) ca: 2.3s (78.0x, -----) dr: 1.9s (63.7x, -----) ma: 0.8s (26.7x, -----)
sarp valgrind-old:0.03s no: 0.6s (19.0x, -3.6%) me: 3.8s (127.0x, 1.3%) ca: 4.7s (156.3x, 0.2%) he:10.7s (356.0x, -0.3%) ca: 2.3s (77.7x, 0.4%) dr: 1.9s (64.7x, -1.6%) ma: 0.8s (27.7x, -3.8%)
-- tinycc --
tinycc valgrind-new:0.44s no: 6.1s (13.8x, -----) me:25.2s (57.2x, -----) ca:52.6s (119.5x, -----) he:21.7s (49.2x, -----) ca:36.7s (83.5x, -----) dr:20.7s (47.0x, -----) ma: 6.0s (13.8x, -----)
tinycc valgrind-old:0.44s no: 5.0s (11.4x, 17.5%) me:22.0s (50.0x, 12.6%) ca:46.7s (106.2x, 11.1%) he:21.8s (49.5x, -0.6%) ca:36.8s (83.7x, -0.3%) dr:25.7s (58.5x,-24.3%) ma: 6.1s (13.8x, -0.3%)
-- Finished tests in perf ----------------------------------------------
== 12 programs, 168 timings =================
5699.48user 44.87system 1:35:50elapsed 99%CPU (0avgtext+0avgdata 532160maxresident)k
0inputs+480872outputs (0major+14764098minor)pagefaults 0swaps
=================================================
./valgrind-new/drd/tests/pth_mutex_signal.stderr.diff
=================================================
--- pth_mutex_signal.stderr.exp 2023-01-09 00:28:09.140492004 -0800
+++ pth_mutex_signal.stderr.out 2023-01-09 00:49:24.268349279 -0800
@@ -6,10 +6,42 @@
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........: clone (in /...libc...)
+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/drd/tests/std_mutex.stderr.diff
=================================================
--- std_mutex.stderr.exp 2023-01-09 00:28:09.130492962 -0800
+++ std_mutex.stderr.out 2023-01-09 00:51:27.146601347 -0800
@@ -1,4 +1,16 @@
-Done.
+terminate called after throwing an instance of 'std::system_error'
+ what(): Enable multithreading to use std::thread: Operation not permitted
+
+Process terminating with default action of signal 6 (SIGABRT)
+ at 0x........: raise (raise.c:?)
+ by 0x........: abort (abort.c:?)
+ by 0x........: __gnu_cxx::__verbose_terminate_handler() (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: ??? (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: std::terminate() (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: __cxa_rethrow (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: void std::vector<std::thread, std::allocator<std::thread> >::_M_emplace_back_aux<main::{lambda()#1}>(main::{lambda()#1}&&) (vector.tcc:426)
+ by 0x........: void std::vector<std::thread, std::allocator<std::thread> >::emplace_back<main::{lambda()#1}>(main::{lambda()#1}&&) (vector.tcc:101)
+ by 0x........: main (std_mutex.cpp:?)
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc04_free_lock.stderr.diff-ppc
=================================================
--- tc04_free_lock.stderr.exp-ppc 2023-01-09 00:28:09.120493920 -0800
+++ tc04_free_lock.stderr.out 2023-01-09 00:51:56.913755319 -0800
@@ -7,28 +7,20 @@
by 0x........: main (tc04_free_lock.c:20)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:26)
+ at 0x........: bar (tc04_free_lock.c:40)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
by 0x........: main (tc04_free_lock.c:26)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: foo (tc04_free_lock.c:47)
- by 0x........: main (tc04_free_lock.c:27)
+ at 0x........: foo (tc04_free_lock.c:49)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc04_free_lock.stderr.diff-s390
=================================================
--- tc04_free_lock.stderr.exp-s390 2023-01-09 00:28:09.130492962 -0800
+++ tc04_free_lock.stderr.out 2023-01-09 00:51:56.913755319 -0800
@@ -8,7 +8,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: ???
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
@@ -16,7 +16,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: foo (tc04_free_lock.c:49)
- by 0x........: ???
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
=================================================
./valgrind-new/drd/tests/tc04_free_lock.stderr.diff-x86
=================================================
--- tc04_free_lock.stderr.exp-x86 2023-01-09 00:28:09.130492962 -0800
+++ tc04_free_lock.stderr.out 2023-01-09 00:51:56.913755319 -0800
@@ -8,7 +8,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:26)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
@@ -16,19 +16,11 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: foo (tc04_free_lock.c:49)
- by 0x........: main (tc04_free_lock.c:27)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-freebsd
=================================================
--- tc09_bad_unlock.stderr.exp-freebsd 2023-01-09 00:28:09.150491046 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -19,9 +19,14 @@
by 0x........: main (tc09_bad_unlock.c:52)
Thread 1:
+The object at address 0x........ is not a mutex.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: nearly_main (tc09_bad_unlock.c:43)
+ by 0x........: main (tc09_bad_unlock.c:52)
+
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:52)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
@@ -37,13 +42,10 @@
by 0x........: nearly_main (tc09_bad_unlock.c:24)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:53)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
+The object at address 0x........ is not a mutex.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-ERROR SUMMARY: 6 errors from 5 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-freebsd-clang
=================================================
--- tc09_bad_unlock.stderr.exp-freebsd-clang 2023-01-09 00:28:09.140492004 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -19,9 +19,14 @@
by 0x........: main (tc09_bad_unlock.c:52)
Thread 1:
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:39)
+The object at address 0x........ is not a mutex.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:52)
+
+Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
+ at 0x........: nearly_main (tc09_bad_unlock.c:48)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
@@ -37,13 +42,10 @@
by 0x........: nearly_main (tc09_bad_unlock.c:24)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:39)
- by 0x........: main (tc09_bad_unlock.c:53)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
+The object at address 0x........ is not a mutex.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-ERROR SUMMARY: 6 errors from 5 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-glibc2.8
=================================================
--- tc09_bad_unlock.stderr.exp-glibc2.8 2023-01-09 00:28:09.130492962 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: (below main)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
- by 0x........: main (tc09_bad_unlock.c:53)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-ppc
=================================================
--- tc09_bad_unlock.stderr.exp-ppc 2023-01-09 00:28:09.130492962 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -25,8 +25,8 @@
by 0x........: main (tc09_bad_unlock.c:52)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:43)
- by 0x........: main (tc09_bad_unlock.c:52)
+ at 0x........: nearly_main (tc09_bad_unlock.c:48)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:43)
- by 0x........: main (tc09_bad_unlock.c:53)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
- by 0x........: main (tc09_bad_unlock.c:53)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-s390
=================================================
--- tc09_bad_unlock.stderr.exp-s390 2023-01-09 00:28:09.140492004 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: ???
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-solaris
=================================================
--- tc09_bad_unlock.stderr.exp-solaris 2023-01-09 00:28:09.120493920 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -6,6 +6,7 @@
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:24)
+ by 0x........: main (tc09_bad_unlock.c:52)
Thread 2:
Mutex not locked by calling thread: mutex 0x........, recursion count 1, owner 1.
@@ -15,19 +16,21 @@
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
+ by 0x........: main (tc09_bad_unlock.c:52)
Thread 1:
The object at address 0x........ is not a mutex.
at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:43)
- by 0x........: main (tc09_bad_unlock.c:5)
+ by 0x........: main (tc09_bad_unlock.c:52)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:52)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
+ by 0x........: main (tc09_bad_unlock.c:52)
---------------------
Mutex not locked by calling thread: mutex 0x........, recursion count 0, owner 1.
@@ -37,18 +40,12 @@
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:24)
+ by 0x........: main (tc09_bad_unlock.c:53)
The object at address 0x........ is not a mutex.
at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:53)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-x86
=================================================
--- tc09_bad_unlock.stderr.exp-x86 2023-01-09 00:28:09.130492962 -0800
+++ tc09_bad_unlock.stderr.out 2023-01-09 00:52:02.543217084 -0800
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:52)
+ by 0x........: (below main)
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:32)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:43)
by 0x........: main (tc09_bad_unlock.c:53)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:48)
- by 0x........: main (tc09_bad_unlock.c:53)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:32)
- by 0x........: main (tc09_bad_unlock.c:53)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/timed_mutex.stderr.diff
=================================================
--- timed_mutex.stderr.exp 2023-01-09 00:28:09.130492962 -0800
+++ timed_mutex.stderr.out 2023-01-09 00:52:55.208181697 -0800
@@ -1,3 +1,16 @@
+terminate called after throwing an instance of 'std::system_error'
+ what(): Enable multithreading to use std::thread: Operation not permitted
+
+Process terminating with default action of signal 6 (SIGABRT)
+ at 0x........: raise (raise.c:?)
+ by 0x........: abort (abort.c:?)
+ by 0x........: __gnu_cxx::__verbose_terminate_handler() (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: ??? (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: std::terminate() (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: __cxa_throw (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: std::thread::_M_start_thread(std::shared_ptr<std::thread::_Impl_base>) (in /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.19)
+ by 0x........: std::thread::thread<void (&)()>(void (&)()) (thread:...)
+ by 0x........: main (timed_mutex.cpp:?)
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-01-09 00:28:08.970508292 -0800
+++ hginfo.stderrB.out 2023-01-09 00:35:10.140155437 -0800
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
@@ -11,6 +12,10 @@
...
Block was alloc'd by thread #x
Lock ga 0x........ {
+ Address 0x........ is 2440 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/gdbserver_tests/hginfo.stdoutB.diff
=================================================
--- hginfo.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ hginfo.stdoutB.out 2023-01-09 00:35:10.080161184 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file hg01_all_ok.c, line 13.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, breakme () at hg01_all_ok.c:13
13 if (shared == 1)
Continuing.
=================================================
./valgrind-new/gdbserver_tests/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2023-01-09 00:28:08.970508292 -0800
+++ hgtls.stdoutB.out 2023-01-09 00:35:13.629821154 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file tls.c, line 55.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
test race tls_ip 0x........ ip 0x........ equal 1
@@ -8,38 +17,8 @@
test race tls_ip 0x........ ip 0x........ equal 1
Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
55 int here = 0;
-test local tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test local tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test global tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test global tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-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 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
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_extern tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_local tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_local tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_global tls_ip 0x........ ip 0x........ equal 1
-Breakpoint 1, tls_ptr (p=0x........) at tls.c:55
-55 int here = 0;
-test so_global tls_ip 0x........ ip 0x........ equal 1
-Program exited normally.
+A debugging session is active.
+ Inferior 1 [Remote target] will be detached.
+Quit anyway? (y or n) [answered Y; input not from terminal]
+Detaching from program: /home/mark/valgrind-nightly/nightly/valgrind-new/none/tests/tls, Remote target
+Ending remote debugging.
=================================================
./valgrind-new/gdbserver_tests/mcblocklistsearch.stderrB.diff
=================================================
--- mcblocklistsearch.stderrB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mcblocklistsearch.stderrB.out 2023-01-09 00:35:15.029687058 -0800
@@ -2,6 +2,16 @@
Breakpoint 1 at 0x........: file leak-tree.c, line 42.
Breakpoint 2 at 0x........: file leak-tree.c, line 68.
Continuing.
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, f () at leak-tree.c:42
42 t->l = mk(); // B
Continuing.
=================================================
./valgrind-new/gdbserver_tests/mcbreak.stderrB.diff
=================================================
--- mcbreak.stderrB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcbreak.stderrB.out 2023-01-09 00:35:16.639532847 -0800
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
vgdb-error value changed from 999999 to 0
n_errs_found 1 n_errs_shown 1 (vgdb-error 0)
n_errs_found 1 n_errs_shown 1 (vgdb-error 0) a
=================================================
./valgrind-new/gdbserver_tests/mcbreak.stdoutB.diff
=================================================
--- mcbreak.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcbreak.stdoutB.out 2023-01-09 00:35:16.579538594 -0800
@@ -1,6 +1,15 @@
Breakpoint 1 at 0x........: file t.c, line 113.
Breakpoint 2 at 0x........: file t.c, line 118.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, main (argc=1, argv=0x........) at t.c:113
113 breakme(__LINE__); //break1
breakme (line=113) at t.c:101
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcclean_after_fork.stderrB.out 2023-01-09 00:35:18.209382468 -0800
@@ -1,3 +1,4 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
monitor command request to kill this process
Remote connection closed
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stdoutB.diff
=================================================
--- mcclean_after_fork.stdoutB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mcclean_after_fork.stdoutB.out 2023-01-09 00:35:18.159387257 -0800
@@ -2,6 +2,15 @@
Breakpoint 2 at 0x........: file clean_after_fork.c, line 20.
Breakpoint 3 at 0x........: file clean_after_fork.c, line 22.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, main () at clean_after_fork.c:9
9 pid = fork();
Hardware read watchpoint 4: mem
=================================================
./valgrind-new/gdbserver_tests/mcinfcallWSRU.stderrB.diff
=================================================
--- mcinfcallWSRU.stderrB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mcinfcallWSRU.stderrB.out 2023-01-09 00:35:24.518778078 -0800
@@ -1,6 +1,16 @@
vgdb-error value changed from 0 to 999999
Breakpoint 1 at 0x........: file sleepers.c, line 73.
Continuing.
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:73
73 int i = 0;
Continuing.
=================================================
./valgrind-new/gdbserver_tests/mcleak.stderrB.diff
=================================================
--- mcleak.stderrB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcleak.stderrB.out 2023-01-09 00:35:36.867595158 -0800
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
10 bytes in 1 blocks are still reachable in loss record ... of ...
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: f (leak-delta.c:15)
=================================================
./valgrind-new/gdbserver_tests/mcleak.stdoutB.diff
=================================================
--- mcleak.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcleak.stdoutB.out 2023-01-09 00:35:36.807600905 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file leak-delta.c, line 10.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, breakme () at leak-delta.c:10
10 static void breakme() {};
#1 0x........ in f () at leak-delta.c:17
=================================================
./valgrind-new/gdbserver_tests/mcmain_pic.stderrB.diff
=================================================
--- mcmain_pic.stderrB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mcmain_pic.stderrB.out 2023-01-09 00:35:38.427445736 -0800
@@ -1 +1,2 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-new/gdbserver_tests/mcmain_pic.stdoutB.diff
=================================================
--- mcmain_pic.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcmain_pic.stdoutB.out 2023-01-09 00:35:38.367451483 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file main_pic.c, line 12.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, main (argc=1, argv=0x........) at main_pic.c:12
12 printf("address of another_func %#" PRIxPTR "\n", (uintptr_t) another_func);
$1 = void
=================================================
./valgrind-new/gdbserver_tests/mcsignopass.stdoutB.diff
=================================================
--- mcsignopass.stdoutB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mcsignopass.stdoutB.out 2023-01-09 00:35:39.987296315 -0800
@@ -5,6 +5,15 @@
Signal Stop Print Pass to program Description
SIGFPE Yes Yes Yes Arithmetic exception
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGSEGV, Segmentation fault.
test1 () at faultstatus.c:117
117 *BADADDR = 'x';
=================================================
./valgrind-new/gdbserver_tests/mcsignopass.stdoutB.diff-freebsd
=================================================
--- mcsignopass.stdoutB.exp-freebsd 2023-01-09 00:28:08.980507334 -0800
+++ mcsignopass.stdoutB.out 2023-01-09 00:35:39.987296315 -0800
@@ -5,6 +5,15 @@
Signal Stop Print Pass to program Description
SIGFPE Yes Yes Yes Arithmetic exception
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGSEGV, Segmentation fault.
test1 () at faultstatus.c:117
117 *BADADDR = 'x';
@@ -52,5 +61,8 @@
SIGSEGV No Yes Yes Segmentation fault
Continuing.
Program received signal SIGSEGV, Segmentation fault.
-Program received signal SIGSEGV, Segmentation fault.
+Program received signal SIGBUS, Bus error.
+test3 () at faultstatus.c:127
+127 mapping[FILESIZE+10];
+Continuing.
Program received signal SIGFPE, Arithmetic exception.
=================================================
./valgrind-new/gdbserver_tests/mcsigpass.stdoutB.diff
=================================================
--- mcsigpass.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcsigpass.stdoutB.out 2023-01-09 00:35:41.467154556 -0800
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGSEGV, Segmentation fault.
test1 () at faultstatus.c:117
117 *BADADDR = 'x';
=================================================
./valgrind-new/gdbserver_tests/mcsigpass.stdoutB.diff-freebsd
=================================================
--- mcsigpass.stdoutB.exp-freebsd 2023-01-09 00:28:08.980507334 -0800
+++ mcsigpass.stdoutB.out 2023-01-09 00:35:41.467154556 -0800
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGSEGV, Segmentation fault.
test1 () at faultstatus.c:117
117 *BADADDR = 'x';
@@ -7,7 +16,7 @@
test2 () at faultstatus.c:122
122 mapping[0] = 'x';
Continuing.
-Program received signal SIGSEGV, Segmentation fault.
+Program received signal SIGBUS, Bus error.
test3 () at faultstatus.c:127
127 mapping[FILESIZE+10];
Continuing.
=================================================
./valgrind-new/gdbserver_tests/mcvabits.stderrB.diff
=================================================
--- mcvabits.stderrB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcvabits.stderrB.out 2023-01-09 00:35:42.847022375 -0800
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
Address 0x........ len 10 addressable
Address 0x........ is 0 bytes inside data symbol "undefined"
Address 0x........ len 10 defined
=================================================
./valgrind-new/gdbserver_tests/mcvabits.stdoutB.diff
=================================================
--- mcvabits.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcvabits.stdoutB.out 2023-01-09 00:35:42.787028122 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file t.c, line 101.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, breakme (line=113) at t.c:101
101 if (line > 1000)
#1 0x........ in main (argc=1, argv=0x........) at t.c:113
=================================================
./valgrind-new/gdbserver_tests/mcwatchpoints.stdoutB.diff
=================================================
--- mcwatchpoints.stdoutB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mcwatchpoints.stdoutB.out 2023-01-09 00:35:44.856829852 -0800
@@ -1,5 +1,14 @@
Breakpoint 1 at 0x........: file watchpoints.c, line 7.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, breakme (line=19) at watchpoints.c:7
7 fprintf(stderr, "breakme function called from line %d\n", line);
Hardware read watchpoint 2: undefined[0]
=================================================
./valgrind-new/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2023-01-09 00:28:08.980507334 -0800
+++ mssnapshot.stderrB.out 2023-01-09 00:35:46.106710123 -0800
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-new/gdbserver_tests/mssnapshot.stdoutB.diff
=================================================
--- mssnapshot.stdoutB.exp 2023-01-09 00:28:08.970508292 -0800
+++ mssnapshot.stdoutB.out 2023-01-09 00:35:46.066713954 -0800
@@ -1,4 +1,13 @@
Breakpoint 1 at 0x........: file t.c, line 106.
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Breakpoint 1, main (argc=1, argv=0x........) at t.c:106
106 char *main_name __attribute__((unused)) = "main name";
=================================================
./valgrind-new/gdbserver_tests/nlcontrolc.stdoutB.diff
=================================================
--- nlcontrolc.stdoutB.exp 2023-01-09 00:28:08.970508292 -0800
+++ nlcontrolc.stdoutB.out 2023-01-09 00:35:53.845968763 -0800
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGTRAP, Trace/breakpoint trap.
do_burn () at sleepers.c:40
40 for (i = 0; i < burn; i++) loopnr++;
=================================================
./valgrind-new/gdbserver_tests/nlcontrolc.stdoutB.diff-freebsd
=================================================
--- nlcontrolc.stdoutB.exp-freebsd 2023-01-09 00:28:08.970508292 -0800
+++ nlcontrolc.stdoutB.out 2023-01-09 00:35:53.845968763 -0800
@@ -1,9 +1,18 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mark/valgrind-nightly/nightly/valgrind-new/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mark/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mark/.gdbinit".
+For more information about this security protection see the
+"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
+ info "(gdb)Auto-loading safe path"
Program received signal SIGTRAP, Trace/breakpoint trap.
do_burn () at sleepers.c:40
40 for (i = 0; i < burn; i++) loopnr++;
- > > > > > > 1
- 3
+ > > > > > >1
+3
$1 = 0
$2 = 1000000
changed burning parameters to sleeping parameters
@@ -15,8 +24,7 @@
reset to sleeping parameters
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
-sleeper_or_burner (v=0x........) at sleepers.c:81
-81 for (i = 0; i < loops; i++) {
-* 1 Thread .... (tid 1 VgTs_Runnable) 0x........ in sleeper_or_burner (v=0x........) at sleepers.c:81
- > > > > 3
+0x........ in syscall ...
+* 1 Thread .... (tid 1 VgTs_WaitSys) 0x........ in syscall ...
+ > > > >4
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
=================================================
./valgrind-new/gdbserver_tests/nlgone_abrt.stderrB.diff
=================================================
--- nlgone_abrt.stderrB.exp 2023-01-09 00:28:08.970508292 -0800
+++ nlgone_abrt.stderrB.out 2023-01-09 00:35:55.945767618 -0800
@@ -0,0 +1 @...
[truncated message content] |