Menu
▾
▴
[Valgrind-testresults] (unchanged) 2025-11-16 11:13:24 CET nightly build (freebsd, FreeBSD 14.3-RELEASE-p5 amd64)
|
From: <pj...@wa...> - 2025-11-16 10:28:50
|
valgrind revision: valgrind-3.27.0.GIT-5f32997518-20251116 C compiler: FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2) GDB: GNU gdb (GDB) 15.1 [GDB v15.1 for FreeBSD] C library: FreeBSD libc uname -mrs: FreeBSD 14.3-RELEASE-p5 amd64 Vendor version: FreeBSD 14.3-RELEASE-p5 Nightly build on freebsd ( FreeBSD 14.3-RELEASE-p5 amd64 ) Started at 2025-11-16 11:13:24 CET Ended at 2025-11-16 11:28:37 CET Results unchanged from 24 hours ago Checking out Valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 947 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/nlvgdbsigqueue (stderr) gdbserver_tests/nlvgdbsigqueue (stdoutB) Last 20 lines of verbose log follow echo -- Finished tests in none/tests/x86 -- Running tests in none/tests/x86-freebsd ---------------------------- bug445032: valgrind -q ./bug445032 -- Finished tests in none/tests/x86-freebsd xml-track-fds: valgrind --track-fds=yes --xml=yes --xml-file=/dev/stderr ./../../tests/true -- 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 == 947 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/nlvgdbsigqueue (stderr) gdbserver_tests/nlvgdbsigqueue (stdoutB) ...checking makefile consistency ...checking header files and include directives gmake: *** [Makefile:1461: regtest] Error 1 ================================================= ./valgrind-new/gdbserver_tests/nlvgdbsigqueue.stderr.diff ================================================= --- nlvgdbsigqueue.stderr.exp 2025-11-16 11:21:49.679939000 +0100 +++ nlvgdbsigqueue.stderr.out 2025-11-16 11:22:52.052801000 +0100 @@ -8,4 +8,3 @@ London ready to sleep and/or burn Petaouchnok ready to sleep and/or burn main ready to sleep and/or burn -Gdb request to kill this process ================================================= ./valgrind-new/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff ================================================= --- nlvgdbsigqueue.stdoutB.exp 2025-11-16 11:21:49.679997000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:22:52.066638000 +0100 @@ -7,10 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -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-new/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff-solaris1 ================================================= --- nlvgdbsigqueue.stdoutB.exp-solaris1 2025-11-16 11:21:49.680019000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:22:52.066638000 +0100 @@ -7,10 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in syscall ... -Kill the program being debugged? (y or n) [answered Y; input not from terminal] ================================================= ./valgrind-new/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff-solaris2 ================================================= --- nlvgdbsigqueue.stdoutB.exp-solaris2 2025-11-16 11:21:49.680040000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:22:52.066638000 +0100 @@ -7,11 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -[New Thread ....] -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in syscall ... -Kill the program being debugged? (y or n) [answered Y; input not from terminal] ================================================= ./valgrind-old/gdbserver_tests/nlvgdbsigqueue.stderr.diff ================================================= --- nlvgdbsigqueue.stderr.exp 2025-11-16 11:13:36.262971000 +0100 +++ nlvgdbsigqueue.stderr.out 2025-11-16 11:16:00.916211000 +0100 @@ -8,4 +8,3 @@ London ready to sleep and/or burn Petaouchnok ready to sleep and/or burn main ready to sleep and/or burn -Gdb request to kill this process ================================================= ./valgrind-old/gdbserver_tests/nlvgdbsigqueue.stdoutB.diff ================================================= --- nlvgdbsigqueue.stdoutB.exp 2025-11-16 11:13:36.263023000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:16:00.930065000 +0100 @@ -7,10 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -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-solaris1 ================================================= --- nlvgdbsigqueue.stdoutB.exp-solaris1 2025-11-16 11:13:36.263044000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:16:00.930065000 +0100 @@ -7,10 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -Program received signal SIGTRAP, Trace/breakpoint trap. -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 2025-11-16 11:13:36.263063000 +0100 +++ nlvgdbsigqueue.stdoutB.out 2025-11-16 11:16:00.930065000 +0100 @@ -7,11 +7,5 @@ sending signal continuing to receive first SIGUSR1 Continuing. -[New Thread ....] -Program received signal SIGUSR1, User defined signal 1. -0x........ in syscall ... +simulate_control_c could not determine the vgdb pid with --vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue continuing to receive second SIGUSR1 -Continuing. -Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in syscall ... -Kill the program being debugged? (y or n) [answered Y; input not from terminal] |
