Summary: | valgrind will hang on OSX 10.11 | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Martin zhao <zhaoming029> |
Component: | memcheck | Assignee: | Rhys Kidd <rhyskidd> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | CC: | hamish+kde, ifteqar7, jseward, pjfloyd, rhyskidd, zhaoming029 |
Priority: | NOR | ||
Version First Reported In: | 3.12 SVN | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin zhao
2016-11-22 08:23:18 UTC
It is hanging after reporting : "UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 16 times)" My program is large and links many other 3rd parties libraries. I am also seeing this when trying to run a large application in valgrind 3.12 on OS X 10.11. I got a few UNKNOWN mach_msg messages on startup, and then my program hung with valgrind using 100% CPU. I waited over 1 hour and it never launched. When i am trying to run my application in valgrind 3.12 on Mac OS X 10.11, i got UNKNOWN mach_msgs and my application did hang. Do we have any solution for this ? 10.11 is long in the tooth now. Can anyone provide a reproducer? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |