https://bugs.kde.org/show_bug.cgi?id=383723
--- Comment #3 from John Reiser <jrei...@bitwagon.com> --- On 09/01/2017 09:18 AM, Andy wrote: > https://bugs.kde.org/show_bug.cgi?id=383723 > > --- Comment #2 from Andy <imol00+...@gmail.com> --- > Is there anything else I can provide to help with this? I'm afraid actually > fixing it is beyond my capabilities. > > (It's a blocker for me - and anyone else trying to use valgrind for Qt-based > apps on macOS it seems.) > > Thanks! > Locate some good documentation on MacOS workq. Specifically, find the MacOS source code which handles all workq options, including those that correspond to the cases in PRE(workq_ops) in coregrind/m_syswrap/syswrap-darwin.c . The closest I could find after modest searching is https://opensource.apple.com/source/xnu/xnu-3789.51.2/bsd/kern/pthread_shims.c.auto.html Apparently there used to be a file pthread_synch.c but I cannot find it. I did find https://opensource.apple.com/source/libpthread/libpthread-137.1.1/kern/workqueue_internal.h which does have #define WQOPS_SET_EVENT_MANAGER_PRIORITY 0x80 /* max() in the provided priority in the the priority of the event manager */ and looks like a clue. If so, then option 128 could be a no-op for valgrind. Try that? -- You are receiving this mail because: You are watching all bug changes.
