https://bugs.kde.org/show_bug.cgi?id=376870
Bug ID: 376870
Summary: The impossible happened on Mavericks 10.9
Product: valgrind
Version: 3.12.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: hamish-...@risingsoftware.com
Target Milestone: ---
I am trying to run my app in memcheck on Mavericks/10.9. (It is actually
running in a 10.9 virtual machine in Parallels 11, because the host is running
Sierra/10.12 which is not supported yet.)
I got quite a few messages about an unhandled syscall:
--10283-- WARNING: unhandled amd64-darwin syscall: unix:446
--10283-- You may be able to write your own handler.
--10283-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--10283-- Nevertheless we consider this a bug. Please report
--10283-- it at http://valgrind.org/support/bug_reports.html.
At the point when I expected my program to crash, I got:
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:
==10283== at 0x238042521: ???
==10283== by 0x238042932: ???
==10283== by 0x238042915: ???
==10283== by 0x2380C13FE: ???
==10283== by 0x2380C0989: ???
==10283== by 0x2380BEDDB: ???
==10283== by 0x2380BCCCD: ???
==10283== by 0x2380CE1CC: ???
sched status:
running_tid=1
and a stack trace.
--
You are receiving this mail because:
You are watching all bug changes.
