https://bugs.kde.org/show_bug.cgi?id=387690
--- Comment #1 from Ben Wiley <therealbenwi...@gmail.com> ---
I get slightly different results when running the same command from the
terminal instead of via CLion:
```bash
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--15943-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--15943-- 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:
==15943== at 0x258052B8B: ???
==15943== by 0x258052F1C: ???
==15943== by 0x258052EF3: ???
==15943== by 0x2580EC414: ???
==15943== by 0x2580EB9F9: ???
==15943== by 0x2580E9C20: ???
==15943== by 0x2580E83E0: ???
==15943== by 0x2580FA29E: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 771)
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.
```
--
You are receiving this mail because:
You are watching all bug changes.
