https://bugs.kde.org/show_bug.cgi?id=383723
--- Comment #27 from Andy <imol00+...@gmail.com> --- Rhys: Thank you for your work on this. Very much appreciated! I applied Alex's patch and ran (1) nulgrind against my test example and (2) nulgrind against small Qt app. It does indeed get past this issue and on to others. On my test example (1), it can't find the dSYM for some reason (or it isn't generated properly): $ valgrind --tool=none ./valgrind-test2.app/Contents/MacOS/valgrind-test2 ==9410== Nulgrind, the minimal Valgrind tool ==9410== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==9410== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==9410== Command: ./valgrind-test2.app/Contents/MacOS/valgrind-test2 ==9410== valgrind: m_debuginfo/debuginfo.c:452 (void discard_or_archive_DebugInfo(DebugInfo *)): Assertion 'is_DebugInfo_active(di)' failed. host stacktrace: ==9410== at 0x258010AFB: ??? ==9410== by 0x258010E9C: ??? ==9410== by 0x258010E73: ??? ... Running nulgrind on a small Qt program (2) gives a new error: $ valgrind --tool=none ./some_app.app/Contents/MacOS/some_app ==9519== Nulgrind, the minimal Valgrind tool ==9519== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==9519== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==9519== Command: ./some_app.app/Contents/MacOS/some_app ==9519== QML debugging is enabled. Only use this in a safe environment. --9519-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --9519-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --9519-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) ==9519== ==9519== Process terminating with default action of signal 11 (SIGSEGV) ==9519== Access not within mapped region at address 0x18 ==9519== at 0x10677D2B1: ??? (in /usr/lib/system/libsystem_pthread.dylib) ==9519== by 0x10677D07C: ??? (in /usr/lib/system/libsystem_pthread.dylib) ==9519== If you believe this happened as a result of a stack ==9519== overflow in your program's main thread (unlikely but ==9519== possible), you can try to increase the size of the ==9519== main thread stack using the --main-stacksize= flag. ==9519== The main thread stack size used in this run was 8388608. --9519:0:schedule VG_(sema_down): read returned -4 ==9519== Segmentation fault: 11 -- You are receiving this mail because: You are watching all bug changes.
