https://bugs.kde.org/show_bug.cgi?id=385279
--- Comment #7 from FX <fxcoud...@gcc.gnu.org> --- No, wrote to fast :) I found another issue: $ /tmp/bin/valgrind /usr/bin/lpq ==55783== Memcheck, a memory error detector ==55783== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==55783== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==55783== Command: /usr/bin/lpq ==55783== --55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) --55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times) ==55783== valgrind: Unrecognised instruction at address 0x1010bfd93. ==55783== at 0x1010BFD93: _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010BDD4F: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010BDD02: dispatch_once_f (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010DBAAE: _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010DB735: _dispatch_kq_drain (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010DAB03: _dispatch_kq_unote_update (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010D5E33: _dispatch_source_refs_register (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010D5F5D: _dispatch_source_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1010CEF49: _dispatch_queue_resume_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==55783== by 0x1014734F6: _notify_lib_init (in /usr/lib/system/libsystem_notify.dylib) ==55783== by 0x101473B89: notify_register_dispatch (in /usr/lib/system/libsystem_notify.dylib) ==55783== by 0x100332C27: CFUserNotificationCreate (in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation) ==55783== Your program just tried to execute an instruction that Valgrind ==55783== did not recognise. There are two possible reasons for this. Several other native Apple programs (Preview, TextEdit) as well as non-Apple (Atom) give the same crash and error stack (with different addresses). -- You are receiving this mail because: You are watching all bug changes.
