https://bugs.kde.org/show_bug.cgi?id=506795
Bug ID: 506795
Summary: Better report which clone flags are problematic
Classification: Developer tools
Product: valgrind
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Currently when calling clone with some unsupported flags you get:
==3508066== Unsupported clone() flags: 0x100111
==3508066==
==3508066== The only supported clone() uses are:
==3508066== - via a threads library (LinuxThreads or NPTL)
==3508066== - via the implementation of fork or vfork
==3508066==
==3508066== Valgrind detected that your program requires
==3508066== the following unimplemented functionality:
==3508066== Valgrind does not support general clone().
==3508066== This may be because the functionality is hard to implement,
==3508066== or because no reasonable program would behave this way,
==3508066== or because nobody has yet needed it. In any case, let us know at
==3508066== www.valgrind.org and/or try to work around the problem, if you can.
==3508066==
==3508066== Valgrind has to exit now. Sorry. Bye!
This doesn't immediately make clear which clone flags are problematic.
In practice it is only a problem for some combination(s) of CLONE_VM CLONE_FS
CLONE_FILES and CLONE_VFORK.
It would be good if the error messages decoded the clone flags and said
precisely what the problematic flag was.
--
You are receiving this mail because:
You are watching all bug changes.
