https://bugs.kde.org/show_bug.cgi?id=509406
Bug ID: 509406
Summary: FreeBSD 15 issues
Classification: Developer tools
Product: valgrind
Version First 3.25 GIT
Reported In:
Platform: Other
OS: FreeBSD
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
FreeBSD 15 has started ALPHA releases:
https://www.freebsd.org/releases/15.0R/schedule/
I'm seeing a couple of failures in a VM.
1. ./memcheck/tests/freebsd/setcred
Has an extra uninit error
--- setcred.stderr.exp 2025-09-12 09:11:53.900540000 +0200
+++ setcred.stderr.out 2025-09-12 09:18:27.818744000 +0200
@@ -20,6 +20,10 @@
by 0x........: main (setcred.cpp:26)
Address 0x........ is not stack'd, malloc'd or (recently) free'd
+Conditional jump or move depends on uninitialised value(s)
+ at 0x........: setcred (in /...libc...)
+ by 0x........: main (setcred.cpp:26)
+
Syscall param setcred(wcred) points to uninitialised byte(s)
at 0x........: setcred (in /...libc...)
by 0x........: main (setcred.cpp:31)
Line 26 is
25 // uninit
26 setcred(flags2, (struct setcred*)x0, size1+x0);
It seems to be the last argument that is causing the problem.
2. none/tests/freebsd/bug452274
This testcase is hanging.
vgstack 58525
Thread 1 (Thread 101470 (tid 1 VgTs_Runnable)):
#0 _write () at _write.S:4
#1 0x0000000000201800 in main (argc=1, argv=0x1fe00009c8) at bug452274.c:31
int main(int argc, char *argv[]) {
setup_timer();
while (ticks < 100) {
write(2, " ", 1);
}
}
It looks like the timer isn't firing (or the signal handler not running) and
the loop above is busy writing to stderr all of the time.
3. none/tests/freebsd/proc_pid_file
+Assertion failed: (rp == resolvedPath2), function main, file
proc_pid_file.cpp, line 20.
This one is easy. It's a new-ish test that requires /proc, which I don't have
on my testing FreeBSD 15 VM.
Fixed.
--
You are receiving this mail because:
You are watching all bug changes.
