|
From: <pj...@wa...> - 2023-01-10 07:18:23
|
valgrind revision: valgrind-3.21.0.GIT-e41dff2999-20230110
C compiler: FreeBSD clang version 13.0.0 (gi...@gi...:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
GDB: GNU gdb (GDB) 12.1 [GDB v12.1 for FreeBSD]
C library: FreeBSD libc
uname -mrs: FreeBSD 13.1-RELEASE-p3 amd64
Vendor version: FreeBSD 13.1-RELEASE-p5
Nightly build on freebsd ( FreeBSD 13.1-RELEASE-p3 amd64 )
Started at 2023-01-10 07:43:36 CET
Ended at 2023-01-10 08:18:05 CET
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
== 775 tests, 2 stderr failures, 1 stdout failure, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/mcclean_after_fork (stdout)
gdbserver_tests/mcclean_after_fork (stderr)
gdbserver_tests/mcclean_after_fork (stdoutB)
gdbserver_tests/mcclean_after_fork (stderrB)
helgrind/tests/tls_threads (stderr)
Last 20 lines of verbose log follow echo
445032: valgrind -q ./445032
-- Finished tests in none/tests/x86-freebsd ----------------------------
-- Finished tests in none/tests ----------------------------------------
-- Running tests in exp-bbv/tests/x86 ---------------------------------
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
million: valgrind --interval-size=100000 --bb-out-file=million.out.bb --pc-out-file=million.out.pc ./million
rep_prefix: valgrind --interval-size=100000 --bb-out-file=rep_prefix.out.bb ./rep_prefix
-- Finished tests in exp-bbv/tests/x86 ---------------------------------
== 775 tests, 2 stderr failures, 1 stdout failure, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/mcclean_after_fork (stdout)
gdbserver_tests/mcclean_after_fork (stderr)
gdbserver_tests/mcclean_after_fork (stdoutB)
gdbserver_tests/mcclean_after_fork (stderrB)
helgrind/tests/tls_threads (stderr)
...checking makefile consistency
...checking header files and include directives
gmake: *** [Makefile:1429: 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
== 775 tests, 2 stderr failures, 1 stdout failure, 13 stderrB failures, 14 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stdoutB)
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mcblocklistsearch (stderrB)
gdbserver_tests/mcbreak (stdoutB)
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stdout)
gdbserver_tests/mcclean_after_fork (stderr)
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/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/nlself_invalidate (stderrB)
gdbserver_tests/nlvgdbsigqueue (stdoutB)
helgrind/tests/tls_threads (stderr)
Last 20 lines of verbose log follow echo
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/nlself_invalidate (stderrB)
gdbserver_tests/nlvgdbsigqueue (stdoutB)
helgrind/tests/tls_threads (stderr)
...checking makefile consistency
...checking header files and include directives
gmake: *** [Makefile:1429: regtest] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Tue Jan 10 08:01:11 2023
--- new.short Tue Jan 10 08:18:05 2023
***************
*** 8,15 ****
! == 775 tests, 2 stderr failures, 1 stdout failure, 13 stderrB failures, 14 stdoutB failures, 0 post failures ==
! gdbserver_tests/hginfo (stdoutB)
! gdbserver_tests/hginfo (stderrB)
! gdbserver_tests/mcblocklistsearch (stderrB)
! gdbserver_tests/mcbreak (stdoutB)
! gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stdout)
--- 8,10 ----
! == 775 tests, 2 stderr failures, 1 stdout failure, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/mcclean_after_fork (stdout)
***************
*** 18,39 ****
gdbserver_tests/mcclean_after_fork (stderrB)
- gdbserver_tests/mcinfcallWSRU (stderrB)
- gdbserver_tests/mcleak (stdoutB)
- gdbserver_tests/mcleak (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/nlself_invalidate (stderrB)
- gdbserver_tests/nlvgdbsigqueue (stdoutB)
helgrind/tests/tls_threads (stderr)
--- 13,14 ----
***************
*** 42,58 ****
Last 20 lines of verbose log follow echo
! 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/nlself_invalidate (stderrB)
! gdbserver_tests/nlvgdbsigqueue (stdoutB)
helgrind/tests/tls_threads (stderr)
--- 17,33 ----
Last 20 lines of verbose log follow echo
! 445032: valgrind -q ./445032
! -- Finished tests in none/tests/x86-freebsd ----------------------------
! -- Finished tests in none/tests ----------------------------------------
! -- Running tests in exp-bbv/tests/x86 ---------------------------------
! 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
! million: valgrind --interval-size=100000 --bb-out-file=million.out.bb --pc-out-file=million.out.pc ./million
! rep_prefix: valgrind --interval-size=100000 --bb-out-file=rep_prefix.out.bb ./rep_prefix
! -- Finished tests in exp-bbv/tests/x86 ---------------------------------
!
! == 775 tests, 2 stderr failures, 1 stdout failure, 1 stderrB failure, 1 stdoutB failure, 0 post failures ==
! gdbserver_tests/mcclean_after_fork (stdout)
! gdbserver_tests/mcclean_after_fork (stderr)
! gdbserver_tests/mcclean_after_fork (stdoutB)
! gdbserver_tests/mcclean_after_fork (stderrB)
helgrind/tests/tls_threads (stderr)
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stderr.diff
=================================================
--- mcclean_after_fork.stderr.exp 2023-01-10 08:01:11.959060000 +0100
+++ mcclean_after_fork.stderr.out 2023-01-10 08:06:17.536848000 +0100
@@ -4,4 +4,8 @@
For a detailed leak analysis, rerun with: --leak-check=full
For lists of detected and suppressed errors, rerun with: -s
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
-Reset valgrind output to log (orderly_finish)
+HEAP SUMMARY:
+ in use at exit: ... bytes in ... blocks
+For a detailed leak analysis, rerun with: --leak-check=full
+For lists of detected and suppressed errors, rerun with: -s
+ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2023-01-10 08:01:11.959114000 +0100
+++ mcclean_after_fork.stderrB.out 2023-01-10 08:06:17.640616000 +0100
@@ -1,3 +1,3 @@
vgdb-error value changed from 0 to 999999
-monitor command request to kill this process
-Remote connection closed
+Expression cannot be implemented with read/access watchpoint.
+"monitor" command not supported by this target.
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stdout.diff
=================================================
--- /dev/null 2023-01-10 08:06:17.495305000 +0100
+++ mcclean_after_fork.stdout.out 2023-01-10 08:06:17.480998000 +0100
@@ -0,0 +1 @@
+mem is zero
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stdoutB.diff
=================================================
--- mcclean_after_fork.stdoutB.exp 2023-01-10 08:01:11.959226000 +0100
+++ mcclean_after_fork.stdoutB.out 2023-01-10 08:06:17.597379000 +0100
@@ -4,9 +4,5 @@
Continuing.
Breakpoint 1, main () at clean_after_fork.c:9
9 pid = fork();
-Hardware read watchpoint 4: mem
Continuing.
-Hardware read watchpoint 4: mem
-Value = 0
-main () at clean_after_fork.c:34
-34 if (mem == 0)
+Program exited normally.
=================================================
./valgrind-new/helgrind/tests/tls_threads.stderr.diff
=================================================
--- tls_threads.stderr.exp 2023-01-10 08:01:11.987016000 +0100
+++ tls_threads.stderr.out 2023-01-10 08:11:38.492202000 +0100
@@ -1,2 +1,126 @@
+--9238:0: sched WARNING: pthread stack cache cannot be disabled!
starting join in main
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: level1 (tls_threads.c:69)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: main (tls_threads.c:88)
+
+----------------------------------------------------------------
+
+Possible data race during read of size 8 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 8 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: level1 (tls_threads.c:69)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during read of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during write of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during read of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: global_false_positive (tls_threads.c:33)
+ by 0x........: level2 (tls_threads.c:49)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during write of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: global_false_positive (tls_threads.c:33)
+ by 0x........: level2 (tls_threads.c:49)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
<truncated beyond 100 lines>
=================================================
./valgrind-old/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-01-10 07:44:12.356926000 +0100
+++ hginfo.stderrB.out 2023-01-10 07:49:18.810462000 +0100
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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
=================================================
./valgrind-old/gdbserver_tests/hginfo.stdoutB.diff
=================================================
--- hginfo.stdoutB.exp 2023-01-10 07:44:12.357040000 +0100
+++ hginfo.stdoutB.out 2023-01-10 07:49:18.769451000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcblocklistsearch.stderrB.diff
=================================================
--- mcblocklistsearch.stderrB.exp 2023-01-10 07:44:12.357639000 +0100
+++ mcblocklistsearch.stderrB.out 2023-01-10 07:49:19.754459000 +0100
@@ -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 "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcbreak.stderrB.diff
=================================================
--- mcbreak.stderrB.exp 2023-01-10 07:44:12.357861000 +0100
+++ mcbreak.stderrB.out 2023-01-10 07:49:20.839976000 +0100
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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-old/gdbserver_tests/mcbreak.stdoutB.diff
=================================================
--- mcbreak.stdoutB.exp 2023-01-10 07:44:12.358047000 +0100
+++ mcbreak.stdoutB.out 2023-01-10 07:49:20.797773000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcclean_after_fork.stderr.diff
=================================================
--- mcclean_after_fork.stderr.exp 2023-01-10 07:44:12.358162000 +0100
+++ mcclean_after_fork.stderr.out 2023-01-10 07:49:21.689757000 +0100
@@ -4,4 +4,8 @@
For a detailed leak analysis, rerun with: --leak-check=full
For lists of detected and suppressed errors, rerun with: -s
ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
-Reset valgrind output to log (orderly_finish)
+HEAP SUMMARY:
+ in use at exit: ... bytes in ... blocks
+For a detailed leak analysis, rerun with: --leak-check=full
+For lists of detected and suppressed errors, rerun with: -s
+ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/gdbserver_tests/mcclean_after_fork.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2023-01-10 07:44:12.358220000 +0100
+++ mcclean_after_fork.stderrB.out 2023-01-10 07:49:21.793675000 +0100
@@ -1,3 +1,4 @@
vgdb-error value changed from 0 to 999999
-monitor command request to kill this process
-Remote connection closed
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
+Expression cannot be implemented with read/access watchpoint.
+"monitor" command not supported by this target.
=================================================
./valgrind-old/gdbserver_tests/mcclean_after_fork.stdout.diff
=================================================
--- /dev/null 2023-01-10 07:49:21.646068000 +0100
+++ mcclean_after_fork.stdout.out 2023-01-10 07:49:21.631790000 +0100
@@ -0,0 +1 @@
+mem is zero
=================================================
./valgrind-old/gdbserver_tests/mcclean_after_fork.stdoutB.diff
=================================================
--- mcclean_after_fork.stdoutB.exp 2023-01-10 07:44:12.358330000 +0100
+++ mcclean_after_fork.stdoutB.out 2023-01-10 07:49:21.750039000 +0100
@@ -2,11 +2,16 @@
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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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
Continuing.
-Hardware read watchpoint 4: mem
-Value = 0
-main () at clean_after_fork.c:34
-34 if (mem == 0)
+Program exited normally.
=================================================
./valgrind-old/gdbserver_tests/mcinfcallWSRU.stderrB.diff
=================================================
--- mcinfcallWSRU.stderrB.exp 2023-01-10 07:44:12.359204000 +0100
+++ mcinfcallWSRU.stderrB.out 2023-01-10 07:49:27.686459000 +0100
@@ -1,6 +1,16 @@
vgdb-error value changed from 0 to 999999
Breakpoint 1 at 0x........: file sleepers.c, line 73.
Continuing.
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcleak.stderrB.diff
=================================================
--- mcleak.stderrB.exp 2023-01-10 07:44:12.359870000 +0100
+++ mcleak.stderrB.out 2023-01-10 07:49:36.639793000 +0100
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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-old/gdbserver_tests/mcleak.stdoutB.diff
=================================================
--- mcleak.stdoutB.exp 2023-01-10 07:44:12.360005000 +0100
+++ mcleak.stdoutB.out 2023-01-10 07:49:36.592016000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcsignopass.stdoutB.diff
=================================================
--- mcsignopass.stdoutB.exp 2023-01-10 07:44:12.360686000 +0100
+++ mcsignopass.stdoutB.out 2023-01-10 07:49:37.646994000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcsignopass.stdoutB.diff-freebsd
=================================================
--- mcsignopass.stdoutB.exp-freebsd 2023-01-10 07:44:12.360747000 +0100
+++ mcsignopass.stdoutB.out 2023-01-10 07:49:37.646994000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcsigpass.stdoutB.diff
=================================================
--- mcsigpass.stdoutB.exp 2023-01-10 07:44:12.361025000 +0100
+++ mcsigpass.stdoutB.out 2023-01-10 07:49:38.648203000 +0100
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcsigpass.stdoutB.diff-freebsd
=================================================
--- mcsigpass.stdoutB.exp-freebsd 2023-01-10 07:44:12.361081000 +0100
+++ mcsigpass.stdoutB.out 2023-01-10 07:49:38.648203000 +0100
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcvabits.stderrB.diff
=================================================
--- mcvabits.stderrB.exp 2023-01-10 07:44:12.361242000 +0100
+++ mcvabits.stderrB.out 2023-01-10 07:49:39.634963000 +0100
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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-old/gdbserver_tests/mcvabits.stdoutB.diff
=================================================
--- mcvabits.stdoutB.exp 2023-01-10 07:44:12.361373000 +0100
+++ mcvabits.stdoutB.out 2023-01-10 07:49:39.591130000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mcwatchpoints.stdoutB.diff
=================================================
--- mcwatchpoints.stdoutB.exp 2023-01-10 07:44:12.361661000 +0100
+++ mcwatchpoints.stdoutB.out 2023-01-10 07:49:40.643379000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2023-01-10 07:44:12.361833000 +0100
+++ mssnapshot.stderrB.out 2023-01-10 07:49:41.473322000 +0100
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/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-old/gdbserver_tests/mssnapshot.stdoutB.diff
=================================================
--- mssnapshot.stdoutB.exp 2023-01-10 07:44:12.362182000 +0100
+++ mssnapshot.stdoutB.out 2023-01-10 07:49:41.446723000 +0100
@@ -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 /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/nlcontrolc.stdoutB.diff
=================================================
--- nlcontrolc.stdoutB.exp 2023-01-10 07:44:12.362472000 +0100
+++ nlcontrolc.stdoutB.out 2023-01-10 07:49:46.117526000 +0100
@@ -1,9 +1,18 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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,7 +24,8 @@
reset to sleeping parameters
Continuing.
Program received signal SIGTRAP, Trace/breakpoint trap.
-0x........ in syscall ...
-* 1 Thread .... (tid 1 VgTs_WaitSys) 0x........ in syscall ...
- > > > >4
+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
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
=================================================
./valgrind-old/gdbserver_tests/nlcontrolc.stdoutB.diff-freebsd
=================================================
--- nlcontrolc.stdoutB.exp-freebsd 2023-01-10 07:44:12.362529000 +0100
+++ nlcontrolc.stdoutB.out 2023-01-10 07:49:46.117526000 +0100
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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-old/gdbserver_tests/nlgone_abrt.stderrB.diff
=================================================
--- nlgone_abrt.stderrB.exp 2023-01-10 07:44:12.362834000 +0100
+++ nlgone_abrt.stderrB.out 2023-01-10 07:49:47.675932000 +0100
@@ -0,0 +1 @@
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-old/gdbserver_tests/nlgone_abrt.stdoutB.diff
=================================================
--- nlgone_abrt.stdoutB.exp 2023-01-10 07:44:12.362966000 +0100
+++ nlgone_abrt.stdoutB.out 2023-01-10 07:49:47.615868000 +0100
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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 SIGABRT, Aborted.
0x........ in syscall ...
Continuing.
=================================================
./valgrind-old/gdbserver_tests/nlgone_exit.stderrB.diff
=================================================
--- nlgone_exit.stderrB.exp 2023-01-10 07:44:12.363100000 +0100
+++ nlgone_exit.stderrB.out 2023-01-10 07:49:48.494469000 +0100
@@ -0,0 +1 @@
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-old/gdbserver_tests/nlgone_return.stderrB.diff
=================================================
--- nlgone_return.stderrB.exp 2023-01-10 07:44:12.363382000 +0100
+++ nlgone_return.stderrB.out 2023-01-10 07:49:49.202116000 +0100
@@ -0,0 +1 @@
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-old/gdbserver_tests/nlgone_return.stdoutB.diff
=================================================
--- nlgone_return.stdoutB.exp 2023-01-10 07:44:12.363514000 +0100
+++ nlgone_return.stdoutB.out 2023-01-10 07:49:49.138148000 +0100
@@ -1,2 +1,11 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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 exited normally.
=================================================
./valgrind-old/gdbserver_tests/nlpasssigalrm.stderrB.diff
=================================================
--- nlpasssigalrm.stderrB.exp 2023-01-10 07:44:12.363687000 +0100
+++ nlpasssigalrm.stderrB.out 2023-01-10 07:49:50.059747000 +0100
@@ -1 +1,2 @@
vgdb-error value changed from 0 to 999999
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-old/gdbserver_tests/nlpasssigalrm.stdoutB.diff
=================================================
--- nlpasssigalrm.stdoutB.exp 2023-01-10 07:44:12.363806000 +0100
+++ nlpasssigalrm.stdoutB.out 2023-01-10 07:49:49.998050000 +0100
@@ -3,6 +3,15 @@
Signal Stop Print Pass to program Description
SIGALRM Yes Yes Yes Alarm clock
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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 SIGALRM, Alarm clock.
0x........ in syscall ...
Signal Stop Print Pass to program Description
=================================================
./valgrind-old/gdbserver_tests/nlself_invalidate.stderrB.diff
=================================================
--- nlself_invalidate.stderrB.exp 2023-01-10 07:44:12.364187000 +0100
+++ nlself_invalidate.stderrB.out 2023-01-10 07:49:50.756733000 +0100
@@ -0,0 +1 @@
+warning: File "/usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
=================================================
./valgrind-old/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff
=================================================
--- nlvgdbsigqueue.stdoutB.exp 2023-01-10 07:44:12.364766000 +0100
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 07:49:58.913539000 +0100
@@ -1,5 +1,14 @@
continuing to have vgdb interrupted by simulate_control_c
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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.
0x........ in syscall ...
attachedwaitingforsigusr1
=================================================
./valgrind-old/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff-solaris1
=================================================
--- nlvgdbsigqueue.stdoutB.exp-solaris1 2023-01-10 07:44:12.364820000 +0100
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 07:49:58.913539000 +0100
@@ -1,5 +1,14 @@
continuing to have vgdb interrupted by simulate_control_c
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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.
0x........ in syscall ...
attachedwaitingforsigusr1
@@ -11,6 +20,6 @@
0x........ in syscall ...
continuing to receive second SIGUSR1
Continuing.
-Program received signal SIGTRAP, Trace/breakpoint trap.
+Program received signal SIGUSR1, User defined signal 1.
0x........ in syscall ...
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
=================================================
./valgrind-old/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff-solaris2
=================================================
--- nlvgdbsigqueue.stdoutB.exp-solaris2 2023-01-10 07:44:12.364873000 +0100
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 07:49:58.913539000 +0100
@@ -1,5 +1,14 @@
continuing to have vgdb interrupted by simulate_control_c
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /usr/home/paulf/scratch/valgrind_nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/paulf/.gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/paulf/.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.
0x........ in syscall ...
attachedwaitingforsigusr1
@@ -7,11 +16,10 @@
sending signal
continuing to receive first SIGUSR1
Continuing.
-[New Thread ....]
Program received signal SIGUSR1, User defined signal 1.
0x........ in syscall ...
continuing to receive second SIGUSR1
Continuing.
-Program received signal SIGTRAP, Trace/breakpoint trap.
+Program received signal SIGUSR1, User defined signal 1.
0x........ in syscall ...
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
=================================================
./valgrind-old/helgrind/tests/tls_threads.stderr.diff
=================================================
--- tls_threads.stderr.exp 2023-01-10 07:44:12.386021000 +0100
+++ tls_threads.stderr.out 2023-01-10 07:54:42.867680000 +0100
@@ -1,2 +1,126 @@
+--42513:0: sched WARNING: pthread stack cache cannot be disabled!
starting join in main
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: level1 (tls_threads.c:69)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: main (tls_threads.c:88)
+
+----------------------------------------------------------------
+
+Possible data race during read of size 8 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 8 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ by 0x........: level1 (tls_threads.c:69)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during read of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during write of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: local_false_positive (tls_threads.c:28)
+ by 0x........: level2 (tls_threads.c:48)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during read of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: global_false_positive (tls_threads.c:33)
+ by 0x........: level2 (tls_threads.c:49)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+----------------------------------------------------------------
+
+Possible data race during write of size 4 at 0x........ by thread #x
+Locks held: none
+ at 0x........: global_false_positive (tls_threads.c:33)
+ by 0x........: level2 (tls_threads.c:49)
+ by 0x........: mythread_wrapper (hg_intercepts.c:...)
+ ...
+
+This conflicts with a previous write of size 4 by thread #x
+Locks held: none
+ ...
+ by 0x........: pthread_create@* (hg_intercepts.c:...)
+ Address 0x........ is in a rw- anonymous segment
+
+---Thread-Announcement------------------------------------------
+
+Thread #x was created
<truncated beyond 100 lines>
|