https://bugs.kde.org/show_bug.cgi?id=503668
Bug ID: 503668
Summary: DRD regtest failures on Fedora 42 amd64
Classification: Developer tools
Product: valgrind
Version: 3.25 GIT
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: drd
Assignee: bart.vanassche+...@gmail.com
Reporter: pjfl...@wanadoo.fr
Target Milestone: ---
I get the following 4 failures
drd/tests/fork-parallel (stderr)
drd/tests/fork-serial (stderr)
drd/tests/threaded-fork-vcs (stderr)
drd/tests/threaded-fork (stder
They all look like lock reinitialization issues. The diff for fork-serial is
+Thread 2:
+Reader-writer lock reinitialization: rwlock 0x.........
+ at 0x........: pthread_rwlock_init (drd_pthread_intercepts.c:?)
+ by 0x........: fork (in /...libc...)
+ by 0x........: startproc (fork.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: clone (in /...libc...)
+rwlock 0x........ was first observed at:
+ at 0x........: pthread_rwlock_rdlock (drd_pthread_intercepts.c:?)
+ by 0x........: _Fork (in /...libc...)
+ by 0x........: fork (in /...libc...)
+ by 0x........: startproc (fork.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: clone (in /...libc...)
+
/bin/ls
+Thread 3:
+Reader-writer lock reinitialization: rwlock 0x.........
+ at 0x........: pthread_rwlock_init (drd_pthread_intercepts.c:?)
+ by 0x........: fork (in /...libc...)
+ by 0x........: startproc (fork.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: clone (in /...libc...)
+rwlock 0x........ was first observed at:
+ at 0x........: pthread_rwlock_rdlock (drd_pthread_intercepts.c:?)
+ by 0x........: _Fork (in /...libc...)
+ by 0x........: fork (in /...libc...)
+ by 0x........: startproc (fork.c:?)
+ by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
+ by 0x........: start_thread
+ by 0x........: clone (in /...libc...)
+
My guess is that this is a glibc 2.41 issue.
--
You are receiving this mail because:
You are watching all bug changes.
