https://bugs.kde.org/show_bug.cgi?id=383811
Remy <remygran...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |remygran...@gmail.com
--- Comment #19 from Remy <remygran...@gmail.com> ---
Hi all,
thanks to @Ben Wiley's instruction, I've finally managed to install Valgrind on
OSX 10.13.2 (17C205).
When I try to execute it, I get the following message :
==28351== Memcheck, a memory error detector
==28351== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==28351== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright
info
==28351== Command: ls -la
==28351==
--28351-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--28351-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--28351-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--28351-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)
eq_SyscallStatus:
{78 0 43}
{78 0 40}
valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt,
SyscallStatus *, SyscallStatus *)): the 'impossible' happened.
host stacktrace:
==28351== at 0x2580540EB: ???
==28351== by 0x25805448C: ???
==28351== by 0x258054463: ???
==28351== by 0x2580EED64: ???
==28351== by 0x2580EE349: ???
==28351== by 0x2580EC570: ???
==28351== by 0x2580EAD23: ???
==28351== by 0x2580FCBEE: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 771)
==28351== at 0x1005B8846: mach_generate_activity_id (in
/usr/lib/system/libsystem_kernel.dylib)
==28351== by 0x1001F4E7A: _voucher_activity_id_allocate_slow (in
/usr/lib/system/libdispatch.dylib)
==28351== by 0x1001F412C: voucher_activity_create_with_data (in
/usr/lib/system/libdispatch.dylib)
==28351== by 0x10061D042: _os_activity_create_addr (in
/usr/lib/system/libsystem_trace.dylib)
==28351== by 0x1003AA1D9: ds_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==28351== by 0x1003A9D1B: si_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==28351== by 0x1003A9DFE: search_item_bynumber (in
/usr/lib/system/libsystem_info.dylib)
==28351== by 0x1003A9D56: search_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==28351== by 0x1003A9D1B: si_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==28351== by 0x1003A923E: getpwuid (in /usr/lib/system/libsystem_info.dylib)
==28351== by 0x10000B6E5: getuser (in
/usr/local/opt/coreutils/libexec/gnubin/ls)
==28351== by 0x100006621: format_user_width (in
/usr/local/opt/coreutils/libexec/gnubin/ls)
==28351== by 0x100004034: gobble_file (in
/usr/local/opt/coreutils/libexec/gnubin/ls)
==28351== by 0x100003262: main (in
/usr/local/opt/coreutils/libexec/gnubin/ls)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
Hope it can helps...
--
You are receiving this mail because:
You are watching all bug changes.
