https://bugs.kde.org/show_bug.cgi?id=481679
Paul Floyd <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Paul Floyd <[email protected]> --- Valgrind doesn't support clone3 that posix_spawn uses on Linux (and on FreeBSD, posix_spawn uses rfork which Valgrind only supports with the posix_spawn options). Sticking to Linux, since Valgrind returns ENONSYS for clone3, glibc falls back to using clone. I'll need to look more at the specifics as to what is happening. However, fork and clone syscalls are very tricky to emulate. For instance, the CLONE_CLEAR_SIGHAND flag would involve turning the flag off initially - the child valgrind needs to keep its signal handlers - and then finding some way to get the child valgrind to clear the signal handlers in its guest. -- You are receiving this mail because: You are watching all bug changes.
