Bug 406681 - Unrecognized instruction _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib)
Summary: Unrecognized instruction _dispatch_kq_poll (in /usr/lib/system/libdispatch.dy...
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.15 SVN
Platform: Compiled Sources macOS
: NOR normal
Target Milestone: ---
Assignee: Rhys Kidd
URL:
Keywords:
: 410562 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-04-19 16:21 UTC by Stephen Eubank
Modified: 2020-05-04 12:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Full output of valgrind -v (53.35 KB, text/plain)
2019-04-19 16:21 UTC, Stephen Eubank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Eubank 2019-04-19 16:21:14 UTC
Created attachment 119507 [details]
Full output of valgrind -v

SUMMARY
 Trying to memcheck my executable compiled under mpicxx gives the following error: 

==68279== valgrind: Unrecognised instruction at address 0x100764b7b.
==68279==    at 0x100764B7B: _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib)

My code runs fine outside valgrind, it is stable, and there are no warnings about bad jumps before the error in valgrind. The instruction seems to be in a system library, so I think the instruction is legitimate.

OBSERVED RESULT

Full output of valgrind -v is attached. 

EXPECTED RESULT


SOFTWARE/OS VERSIONS

Valgrind 3.15.0 downloaded and built today, tested with 'valgrind ls -L'.

mpicxx --version:
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

My executable compiled with:
mpicxx -std=c++11 -g -O3 ...  -lstdc++

uname -a:
Darwin Biocomplexitys-Eubank.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64 x86_64
Comment 1 Rhys Kidd 2019-10-03 06:12:39 UTC
*** Bug 410562 has been marked as a duplicate of this bug. ***