https://bugs.kde.org/show_bug.cgi?id=373192
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #2 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Looking at the differences between 2.23 and 2.24, I suspect the problem
is created because 2.24 is implementing posix_spawn(p) using
clone (CLONE_VM| CLONE_VFORK), while 2.23 uses fork or vfork.
Valgrind does not implement vfork, it just considers vfork is a fork,
hoping for the best.
It looks like the new glibc posix_spawn implementation depends more
on the precise semantic of vfork (or more exactly, of clone(CLONE_VM|
CLONE_VFORK),
such as sharing address space and/or having the calling thread suspended
waiting for the child to exec or exit.
If the dependency is only on the 'being suspended" aspect, that might
be relatively easy to fix.
Hwoever, from the trace, it looks like both the parent and the child
have executed the fprintf. Not very clear how that can happen.
Can you run with --trace-syscalls=yes --trace-children=yes --time-stamp=yes
and attach the resulting trace ?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
