The jemalloc memory allocator uses the syscalls unix:520 and unix:521 on macosx, but these are not handled by valgrind. This leads to a lot of warnings while running the tests under valgrind. This problem is reported in jemalloc upstream: https://github.com/jemalloc/jemalloc/issues/1274 Also, running jemalloc under valgrind works fine on Linux, but some of the test crash on MacOSX with a SIGILL. The instruction to reproduce both the warnings and the crash are in the github issue linked above.
The syscalls 520 and 521 might be these ones (https://github.com/apple/darwin-xnu/blob/master/bsd/kern/syscalls.master#L824): AUE_KILL and AUE_EXIT .
In the CI log you provided, I only see mention of the following missing syscall: * unhandled amd64-darwin syscall: unix:515 (ulock_wait) the previously missing ulock_wait() syscall was just added to Valgrind git master today, so can you please retry with a git version? Where did you see unix:520 and unix:521 missing on macOS with jemalloc?
(In reply to Gonzalo BG from comment #1) > The syscalls 520 and 521 might be these ones > (https://github.com/apple/darwin-xnu/blob/master/bsd/kern/syscalls. > master#L824): AUE_KILL and AUE_EXIT . The unix syscalls are 520 (terminate_with_payload) and 521 (abort_with_payload)
> Where did you see unix:520 and unix:521 missing on macOS with jemalloc? Going through the logs and travis-CI runs I can't find them anywhere. Maybe I saw this locally, no idea. I just re-started CI with the master branch and it seems that the unhandled syscall messages have disappeared: https://travis-ci.org/jemalloc/jemalloc/jobs/418209262
Looking at that CI log it's now much cleaner. The major issue is the _pthread_body crashes, which are known and being tracked in bz#379893. I'll merge this bug report into bz#379893, as you can continue to follow progress there. If you do see new, different Valgrind error reports - please open a new bug report. -- Thanks by the way for running Valgrind-enabled macOS CI versions of jemalloc. These low-level memory test suites are good for flushing out interesting corner cases in Valgrind's macOS support! *** This bug has been marked as a duplicate of bug 379893 ***
Thank you for looking into it! I'll follow the other bug.