https://bugs.kde.org/show_bug.cgi?id=423963
Tom Hughes changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #31 from Christoph Cullmann ---
(In reply to Paul Floyd from comment #30)
> (In reply to Tom Hughes from comment #28)
> > I think I know what's happening - the POST handler for clone is actually
> > running in both threads.
> >
> > It works
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #30 from Paul Floyd ---
(In reply to Tom Hughes from comment #28)
> I think I know what's happening - the POST handler for clone is actually
> running in both threads.
>
> It works in the parent thread but when it tries to read the PIDFD in
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #29 from Christoph Cullmann ---
Yeah ;=)
./vg-in-place /home/cullmann/test/test
master
==39129== Memcheck, a memory error detector
==39129==
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #28 from Tom Hughes ---
I think I know what's happening - the POST handler for clone is actually
running in both threads.
It works in the parent thread but when it tries to read the PIDFD in the child
thread it gets a nonsense value. Possib
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #27 from Tom Hughes ---
Those both look correct in the strace - we have:
clone(child_stack=NULL, flags=CLONE_PIDFD|SIGCHLD, parent_tid=[12]) = 8063
and:
clone(child_stack=NULL, flags=CLONE_PIDFD|SIGCHLD, parent_tid=[12]) = 8050
but when
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #26 from Thiago Macieira ---
That diff shows the original mistake in calling clone() without SIGCHLD.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #25 from Christoph Cullmann ---
As additional info that might be useful:
Before we ported our stuff to Qt 6.x, we did use Qt 5.15 (not with all
patches).
There we never had such issues, below is the diff of the 3rdparty/forkfd
directories
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #24 from Christoph Cullmann ---
Created attachment 137387
--> https://bugs.kde.org/attachment.cgi?id=137387&action=edit
strace for "failing" 6.1 run
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #23 from Christoph Cullmann ---
Created attachment 137386
--> https://bugs.kde.org/attachment.cgi?id=137386&action=edit
strace for "successful" 6.0 run
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #22 from Christoph Cullmann ---
(In reply to Tom Hughes from comment #21)
> Hmm.. It doesn't seem to make a huge amount of sense. Both versions of Qt
> are using PIDFD but with 6.1 the FD we get from the kernel seems to be a
> silly number t
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #21 from Tom Hughes ---
Hmm.. It doesn't seem to make a huge amount of sense. Both versions of Qt are
using PIDFD but with 6.1 the FD we get from the kernel seems to be a silly
number that is not a valid file descriptor triggering everything
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #20 from Thiago Macieira ---
(In reply to Christoph Cullmann from comment #19)
> I compiled now the 6.1 branch locally with
>
> -DFEATURE_forkfd_pidfd=OFF
>
> That triggers (at least if I don't read the Qt sources wrongly)
>
> int ffd
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #19 from Christoph Cullmann ---
I compiled now the 6.1 branch locally with
-DFEATURE_forkfd_pidfd=OFF
That triggers (at least if I don't read the Qt sources wrongly)
int ffdflags = FFD_CLOEXEC;
// QTBUG-86285
#if !QT_CONFIG(forkf
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #18 from Thiago Macieira ---
Yes, Qt uses CLONE_PIDFD. It was the first user of this feature (the feature
was written from our prompting and design). The flag has changed slightly since
the first time this bug was reported. It is now CLONE_P
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #17 from Christoph Cullmann ---
Created attachment 137384
--> https://bugs.kde.org/attachment.cgi?id=137384&action=edit
valgrind 3.17.0 run with Qt 6.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #16 from Christoph Cullmann ---
Created attachment 137383
--> https://bugs.kde.org/attachment.cgi?id=137383&action=edit
valgrind 3.17.0 run with Qt 6.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #15 from Christoph Cullmann ---
Sorry, didn't want to spam you.
I will attach a --trace-syscalls=yes ./test log for both the working 6.0 and
non-working 6.1 run.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #14 from Tom Hughes -
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #13 from Christoph Cullmann ---
Just tried the test example with our Qt 6.1 build:
/makefactory/usr/heute/144702/release/linux64/bin/valgrind ./test
==494853== Memcheck, a memory error detector
==494853== Copyright (C) 2002-2017, a
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #12 from Christoph Cullmann ---
For better testing, I added a minimal Qt 6 example.
The tar contains the CMakeLists.txt + test.cpp.
(and an example compile against the system Qt 6.0.2 of Manjaro)
If I use the system 3.16.1 valgrind of Man
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #11 from Christoph Cullmann ---
Created attachment 137380
--> https://bugs.kde.org/attachment.cgi?id=137380&action=edit
Minimal Qt 6 example
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #10 from Christoph Cullmann ---
Here is the full log of one 3.17.0 run, compiled without any extra
flags/patches from the source tarball with the system gcc (GCC) 10.2.0 on
Manjaro:
# disable PCRE jit
export QT_ENABLE_REGEXP_JIT=0
# run th
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #9 from Christoph Cullmann ---
I tried now my 6.1 Qt application again.
There with 3.16.1 I still get (even if self compiled):
valgrind: m_syswrap/syswrap-main.c:1957 (vgPlain_client_syscall): Assertion '0
== (sci->flags & ~(SfMayBlock | S
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #8 from Christoph Cullmann ---
Hmm, you are right, if I use 3.16.1 + apply the one patch here to fix the
compile
https://raw.githubusercontent.com/archlinux/svntogit-packages/packages/valgrind/trunk/valgrind-3.16-openmpi-4.0.patch
it still w
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #7 from Christoph Cullmann ---
Hmm, I think this is the current pkgbuild file:
https://github.com/archlinux/svntogit-packages/blob/760e4b1e68f1880e01a6f4d425c988134dafe84b/trunk/PKGBUILD
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #6 from Paul Floyd ---
I don't know what the root cause is exactly of this issue. My suspicion is that
it is related to the LTO used in producing the official Valgrind package. If
that is the case then waiting for the next official release m
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #5 from Christoph Cullmann ---
I would wait for official 3.17 distro packages to try again, then I would close
this, if it works there, too.
Is that ok for you?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423963
--- Comment #4 from Christoph Cullmann ---
Ok, just tried it, system is up-to-date Manjaro.
I downloaded now
https://sourceware.org/pub/valgrind/valgrind-3.17.0.tar.bz2
and do like you told below ;)
I think 3.17 fixes the issue for me, at least, my
https://bugs.kde.org/show_bug.cgi?id=423963
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #3 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=423963
Christoph Cullmann changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #2 from Chris
https://bugs.kde.org/show_bug.cgi?id=423963
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Summary|Cannot spawn
32 matches
Mail list logo
