Otherwise this will fail:
$ valgrind ./src/bitcoind -regtest -datadir=/tmp -sandbox=log-and-abort
==204660== Memcheck, a memory error detector
==204660== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==204660== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==204660== Command: ./src/bitcoind -regtest -datadir=/tmp -sandbox=log-and-abort
==204660==
Bad system call (core dumped)
I presume valgrind isn't supported @practicalswift ?
This config isn't run by any CI task in this repo, but I use it outside
Concept ACK. I would guess that this doesn't work because valgrind will instrument the process with its own code, which uses system calls that are not allowed by the sandbox.
Good catch!
cr ACK fa44406ffd34670af929f14484042e1de29ffcdd
I would guess that this doesn't work because valgrind will instrument the process with its own code, which uses system calls that are not allowed by the sandbox.
Exactly! Same thing with libFuzzer and some sanitizers - that's why we do this in configure.ac:
AC_MSG_WARN(Specifying --with-sanitizers forces --without-seccomp since the sanitizers
introduce use of syscalls not allowed by the bitcoind syscall sandbox (-sandbox=<mode>).)