|
From: <ma...@bu...> - 2023-01-10 01:34:25
|
valgrind revision: valgrind-3.21.0.GIT-e41dff2999-20230110
C compiler: gcc (GCC) 12.2.1 20220819 (Red Hat 12.2.1-2)
GDB: GNU gdb (GDB) Fedora 12.1-2.fc36
Assembler: GNU assembler version 2.37-36.fc36
C library: GNU C Library (GNU libc) stable release version 2.35.
uname -mrs: Linux 6.0.5-200.fc36.s390x s390x
Vendor version: Fedora Linux 36 (Thirty Six)
Nightly build on lfedora1 ( Fedora release 36 (Thirty Six), s390x )
Started at 2023-01-10 00:00:01 UTC
Ended at 2023-01-10 01:33:48 UTC
Results differ from 24 hours ago
Checking out Valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 792 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
Last 20 lines of verbose log follow echo
syslog: valgrind -q ./syslog
system: valgrind ./system
thread-exits: valgrind ./thread-exits
threaded-fork: valgrind ./threaded-fork
threadederrno: valgrind -q ./threadederrno
timestamp: valgrind --time-stamp=yes ./timestamp
tls: valgrind ./tls
unit_debuglog: valgrind -q ./unit_debuglog
vgprintf: valgrind ./vgprintf
vgprintf_nvalgrind: valgrind ./vgprintf_nvalgrind
-- Finished tests in none/tests ----------------------------------------
== 792 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [Makefile: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
== 792 tests, 3 stderr failures, 0 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/linux/timerfd-syscall (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
Last 20 lines of verbose log follow echo
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/linux/timerfd-syscall (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
drd/tests/pth_mutex_signal (stderr)
...checking makefile consistency
...checking header files and include directives
make: *** [Makefile:1429: regtest] Error 1
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short 2023-01-10 00:55:54.425836030 +0000
--- new.short 2023-01-10 01:33:48.487271317 +0000
***************
*** 8,40 ****
! == 792 tests, 3 stderr failures, 0 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/linux/timerfd-syscall (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
--- 8,11 ----
! == 792 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
***************
*** 44,59 ****
Last 20 lines of verbose log follow echo
! 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/linux/timerfd-syscall (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
--- 15,30 ----
Last 20 lines of verbose log follow echo
! syslog: valgrind -q ./syslog
! system: valgrind ./system
! thread-exits: valgrind ./thread-exits
! threaded-fork: valgrind ./threaded-fork
! threadederrno: valgrind -q ./threadederrno
! timestamp: valgrind --time-stamp=yes ./timestamp
! tls: valgrind ./tls
! unit_debuglog: valgrind -q ./unit_debuglog
! vgprintf: valgrind ./vgprintf
! vgprintf_nvalgrind: valgrind ./vgprintf_nvalgrind
! -- Finished tests in none/tests ----------------------------------------
!
! == 792 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
! gdbserver_tests/hginfo (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
=================================================
./valgrind-new/drd/tests/pth_mutex_signal.stderr.diff
=================================================
--- pth_mutex_signal.stderr.exp 2023-01-10 00:55:56.145836030 +0000
+++ pth_mutex_signal.stderr.out 2023-01-10 01:23:41.806730389 +0000
@@ -6,10 +6,43 @@
signalling
sleeping
nullHandler running
-unlocking
+Thread 2:
+The impossible happened: mutex is locked simultaneously by two threads: mutex 0x........, recursion count 1, owner 1.
+ at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
+ by 0x........: contender_start (pth_mutex_signal.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: ??? (in /...libc...)
+ by 0x........: ???
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
contender locked mutex
contender unlocking mutex
contender unlocked mutex
+unlocking
+Thread 1:
+Mutex not locked by calling thread: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
joining thread
+Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_join (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
+Destroying locked mutex: mutex 0x........, recursion count 1, owner 0.
+ at 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-01-10 00:55:57.395836030 +0000
+++ hginfo.stderrB.out 2023-01-10 01:04:47.525803139 +0000
@@ -1,5 +1,9 @@
vgdb-error value changed from 0 to 999999
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
@@ -11,6 +15,10 @@
...
Block was alloc'd by thread #x
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
=================================================
./valgrind-new/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2023-01-10 00:55:59.315836030 +0000
+++ vbit-test.stderr.out 2023-01-10 01:14:35.086281993 +0000
@@ -0,0 +1,3 @@
+Conditional jump or move depends on uninitialised value(s)
+ ...
+
=================================================
./valgrind-old/drd/tests/pth_mutex_signal.stderr.diff
=================================================
--- pth_mutex_signal.stderr.exp 2023-01-10 00:00:35.537202704 +0000
+++ pth_mutex_signal.stderr.out 2023-01-10 00:43:40.275877474 +0000
@@ -6,10 +6,43 @@
signalling
sleeping
nullHandler running
-unlocking
+Thread 2:
+The impossible happened: mutex is locked simultaneously by two threads: mutex 0x........, recursion count 1, owner 1.
+ at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
+ by 0x........: contender_start (pth_mutex_signal.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: ??? (in /...libc...)
+ by 0x........: ???
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
contender locked mutex
contender unlocking mutex
contender unlocked mutex
+unlocking
+Thread 1:
+Mutex not locked by calling thread: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_mutex_unlock (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
joining thread
+Mutex still locked at thread exit: mutex 0x........, recursion count 1, owner 2.
+ at 0x........: pthread_join (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
+Destroying locked mutex: mutex 0x........, recursion count 1, owner 0.
+ at 0x........: main (pth_mutex_signal.c:?)
+mutex 0x........ was first observed at:
+ at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
+ by 0x........: main (pth_mutex_signal.c:?)
+
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ hginfo.stderrB.out 2023-01-10 00:13:26.356980452 +0000
@@ -1,4 +1,9 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
@@ -11,6 +16,10 @@
...
Block was alloc'd by thread #x
Lock ga 0x........ {
+ Address 0x........ is 2648 bytes inside data symbol "_rtld_local"
+ kind mbRec
+}
+Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
{ W1:thread #x tid #x }
=================================================
./valgrind-old/gdbserver_tests/hginfo.stdoutB.diff
=================================================
--- hginfo.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ hginfo.stdoutB.out 2023-01-10 00:13:26.196980452 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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/hgtls.stdoutB.diff
=================================================
--- hgtls.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ hgtls.stdoutB.out 2023-01-10 00:13:33.906980452 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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
=================================================
./valgrind-old/gdbserver_tests/mcblocklistsearch.stderrB.diff
=================================================
--- mcblocklistsearch.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcblocklistsearch.stderrB.out 2023-01-10 00:13:37.156980452 +0000
@@ -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/mjw/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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcbreak.stderrB.out 2023-01-10 00:13:43.206980452 +0000
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ mcbreak.stdoutB.out 2023-01-10 00:13:42.986980452 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcclean_after_fork.stderrB.out 2023-01-10 00:13:47.286980452 +0000
@@ -1,3 +1,4 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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".
monitor command request to kill this process
Remote connection closed
=================================================
./valgrind-old/gdbserver_tests/mcclean_after_fork.stdoutB.diff
=================================================
--- mcclean_after_fork.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcclean_after_fork.stdoutB.out 2023-01-10 00:13:47.206980452 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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-old/gdbserver_tests/mcinfcallWSRU.stderrB.diff
=================================================
--- mcinfcallWSRU.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcinfcallWSRU.stderrB.out 2023-01-10 00:13:58.866980452 +0000
@@ -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/mjw/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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcleak.stderrB.out 2023-01-10 00:14:13.756970806 +0000
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ mcleak.stdoutB.out 2023-01-10 00:14:13.416970806 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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/mcmain_pic.stderrB.diff
=================================================
--- mcmain_pic.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcmain_pic.stderrB.out 2023-01-10 00:14:17.766870172 +0000
@@ -1 +1,2 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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/mcmain_pic.stdoutB.diff
=================================================
--- mcmain_pic.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcmain_pic.stdoutB.out 2023-01-10 00:14:17.196870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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-old/gdbserver_tests/mcsignopass.stdoutB.diff
=================================================
--- mcsignopass.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ mcsignopass.stdoutB.out 2023-01-10 00:14:22.146870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcsignopass.stdoutB.out 2023-01-10 00:14:22.146870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcsigpass.stdoutB.out 2023-01-10 00:14:25.926870172 +0000
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcsigpass.stdoutB.out 2023-01-10 00:14:25.926870172 +0000
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcvabits.stderrB.out 2023-01-10 00:14:29.356870172 +0000
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ mcvabits.stdoutB.out 2023-01-10 00:14:29.266870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mcwatchpoints.stdoutB.out 2023-01-10 00:14:33.636870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ mssnapshot.stderrB.out 2023-01-10 00:14:35.986870172 +0000
@@ -1,4 +1,5 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ mssnapshot.stdoutB.out 2023-01-10 00:14:35.926870172 +0000
@@ -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/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ nlcontrolc.stdoutB.out 2023-01-10 00:14:44.806870172 +0000
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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/nlcontrolc.stdoutB.diff-freebsd
=================================================
--- nlcontrolc.stdoutB.exp-freebsd 2023-01-10 00:00:35.547202704 +0000
+++ nlcontrolc.stdoutB.out 2023-01-10 00:14:44.806870172 +0000
@@ -1,9 +1,18 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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-old/gdbserver_tests/nlgone_abrt.stderrB.diff
=================================================
--- nlgone_abrt.stderrB.exp 2023-01-10 00:00:35.547202704 +0000
+++ nlgone_abrt.stderrB.out 2023-01-10 00:14:48.706870172 +0000
@@ -0,0 +1 @@
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ nlgone_abrt.stdoutB.out 2023-01-10 00:14:47.236870172 +0000
@@ -1,4 +1,13 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ nlgone_exit.stderrB.out 2023-01-10 00:14:50.456870172 +0000
@@ -0,0 +1 @@
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ nlgone_return.stderrB.out 2023-01-10 00:14:52.486870172 +0000
@@ -0,0 +1 @@
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ nlgone_return.stdoutB.out 2023-01-10 00:14:51.886870172 +0000
@@ -1,2 +1,11 @@
Continuing.
+To enable execution of this file add
+ add-auto-load-safe-path /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ nlpasssigalrm.stderrB.out 2023-01-10 00:14:54.916870172 +0000
@@ -1 +1,2 @@
vgdb-error value changed from 0 to 999999
+warning: File "/home/mjw/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 00:00:35.547202704 +0000
+++ nlpasssigalrm.stdoutB.out 2023-01-10 00:14:54.086870172 +0000
@@ -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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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/nlvgdbsigqueue.stdoutB.diff
=================================================
--- nlvgdbsigqueue.stdoutB.exp 2023-01-10 00:00:35.547202704 +0000
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 00:15:08.386870172 +0000
@@ -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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 00:15:08.386870172 +0000
@@ -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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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 00:00:35.547202704 +0000
+++ nlvgdbsigqueue.stdoutB.out 2023-01-10 00:15:08.386870172 +0000
@@ -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 /home/mjw/valgrind-nightly/nightly/valgrind-old/Inst/libexec/valgrind/valgrind-monitor.py
+line to your configuration file "/home/mjw/.config/gdb/gdbinit".
+To completely disable this security protection add
+ set auto-load safe-path /
+line to your configuration file "/home/mjw/.config/gdb/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/memcheck/tests/linux/timerfd-syscall.stderr.diff
=================================================
--- timerfd-syscall.stderr.exp 2023-01-10 00:00:35.597202704 +0000
+++ timerfd-syscall.stderr.out 2023-01-10 00:20:28.126553665 +0000
@@ -33,7 +33,7 @@
got timer ticks (1) after 0.5 s
absolute timer test (at 500 ms) ...
waiting timer ...
-got timer ticks (1) after 0.5 s
+got timer ticks (1) after 0.6 s
sequential timer test (100 ms clock) ...
sleeping one second ...
timerfd_gettime returned:
@@ -43,7 +43,7 @@
got about 20 timer ticks after about 2s
O_NONBLOCK test ...
waiting timer (flush the single tick) ...
-got timer ticks (1) after 0.1 s
+got timer ticks (1) after 0.3 s
success
HEAP SUMMARY:
=================================================
./valgrind-old/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2023-01-10 00:00:35.677202704 +0000
+++ vbit-test.stderr.out 2023-01-10 00:31:41.605877474 +0000
@@ -0,0 +1,3 @@
+Conditional jump or move depends on uninitialised value(s)
+ ...
+
|