https://bugs.kde.org/show_bug.cgi?id=398086
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #1 from Mark Wielaard <m...@klomp.org> ---
Relevant part of the log:
--172-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--172-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times)
--172-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times)
--172-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times)
--172-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 16 times)
--172-- WARNING: unhandled amd64-darwin syscall: unix:463
==172== at 0x10210B8C2: openat (in /usr/lib/system/libsystem_kernel.dylib)
==172== by 0x102174733: _os_trace_read_file_at (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x10217494B: _os_trace_read_plist_at (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x1021702A0: _os_log_preferences_load (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x10217100F: _os_log_preferences_refresh (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x102170BBB: os_log_create (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x104A270B5: __SLSLogInit_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x104B175E7: __SLSInitialize_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
--172-- You may be able to write your own handler.
--172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--172-- Nevertheless we consider this a bug. Please report
--172-- it at http://valgrind.org/support/bug_reports.html.
--172-- WARNING: unhandled amd64-darwin syscall: unix:463
==172== at 0x10210B8C2: openat (in /usr/lib/system/libsystem_kernel.dylib)
==172== by 0x102174733: _os_trace_read_file_at (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x10217494B: _os_trace_read_plist_at (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x102170360: _os_log_preferences_load (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x10217100F: _os_log_preferences_refresh (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x102170BBB: os_log_create (in
/usr/lib/system/libsystem_trace.dylib)
==172== by 0x104A270B5: __SLSLogInit_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x104B175E7: __SLSInitialize_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
--172-- You may be able to write your own handler.
--172-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--172-- Nevertheless we consider this a bug. Please report
--172-- it at http://valgrind.org/support/bug_reports.html.
==172== valgrind: Unrecognised instruction at address 0x101c8bdfc.
==172== at 0x101C8BDFC: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA7ABA: _dispatch_kq_poll (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA7741: _dispatch_kq_drain (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA6B0F: _dispatch_kq_unote_update (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA1E3E: _dispatch_source_refs_register (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA1F68: _dispatch_source_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C9AF54: _dispatch_queue_resume_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x1049DCEF5: (anonymous namespace)::RunElsewhere::instance() (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x104B17565: __SLSInitialize_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== Your program just tried to execute an instruction that Valgrind
==172== did not recognise. There are two possible reasons for this.
==172== 1. Your program has a bug and erroneously jumped to a non-code
==172== location. If you are running Memcheck and you just saw a
==172== warning about a bad jump, it's probably your program's fault.
==172== 2. The instruction is legitimate but Valgrind doesn't handle it,
==172== i.e. it's Valgrind's fault. If you think this is the case or
==172== you are not sure, please let us know and we'll try to fix it.
==172== Either way, Valgrind will now raise a SIGILL signal which will
==172== probably kill your program.
==172==
==172== Process terminating with default action of signal 4 (SIGILL)
==172== Illegal opcode at address 0x101C8BDFC
==172== at 0x101C8BDFC: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C89D6A: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA7ABA: _dispatch_kq_poll (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA7741: _dispatch_kq_drain (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA6B0F: _dispatch_kq_unote_update (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA1E3E: _dispatch_source_refs_register (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101CA1F68: _dispatch_source_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x101C9AF54: _dispatch_queue_resume_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==172== by 0x1049DCEF5: (anonymous namespace)::RunElsewhere::instance() (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x104B17565: __SLSInitialize_block_invoke (in
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight)
==172== by 0x101C89DB7: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==172==
So it could be some issue with the unknown syscalls. It would also be helpful
to have the disassembly from at 0x101C8BDFC: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib) to know which instruction it precisely is.
--
You are receiving this mail because:
You are watching all bug changes.
