bitcoin/ci/test/00_setup_env_native_fuzz_with_valgrind.sh

#!/usr/bin/env bash
#
# Copyright (c) 2019-2022 The Bitcoin Core developers
# Distributed under the MIT software license, see the accompanying
# file COPYING or http://www.opensource.org/licenses/mit-license.php.

export LC_ALL=C.UTF-8

export DOCKER_NAME_TAG="ubuntu:22.04"
export CONTAINER_NAME=ci_native_fuzz_valgrind
export PACKAGES="clang llvm python3 libevent-dev bsdmainutils libboost-dev libsqlite3-dev valgrind"
export NO_DEPENDS=1
export RUN_UNIT_TESTS=false
export RUN_FUNCTIONAL_TESTS=false
export RUN_FUZZ_TESTS=true
export FUZZ_TESTS_CONFIG="--valgrind"
export GOAL="install"
# Temporarily pin dwarf 4, until valgrind can understand clang's dwarf 5
export BITCOIN_CONFIG="--enable-fuzz --with-sanitizers=fuzzer CC=clang CXX=clang++ CFLAGS='-gdwarf-4' CXXFLAGS='-gdwarf-4'"
export CCACHE_SIZE=200M
ci: Run fuzz testing test cases under valgrind 2020-02-17 13:34:51 +00:00			`#!/usr/bin/env bash`
			`#`
scripted-diff: Bump copyright headers -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./ -END VERIFY SCRIPT- Commits of previous years: - 2021: f47dda2c58b5d8d623e0e7ff4e74bc352dfa83d7 - 2020: fa0074e2d82928016a43ca408717154a1c70a4db - 2019: aaaaad6ac95b402fe18d019d67897ced6b316ee0 2022-12-24 23:49:50 +00:00			`# Copyright (c) 2019-2022 The Bitcoin Core developers`
ci: Run fuzz testing test cases under valgrind 2020-02-17 13:34:51 +00:00			`# Distributed under the MIT software license, see the accompanying`
			`# file COPYING or http://www.opensource.org/licenses/mit-license.php.`

			`export LC_ALL=C.UTF-8`

ci: Bump fuzz tasks to jammy This gives them a newer clang version, which may have more sanitizers available. 2022-02-08 20:24:47 +01:00			`export DOCKER_NAME_TAG="ubuntu:22.04"`
ci: Run fuzz testing test cases under valgrind 2020-02-17 13:34:51 +00:00			`export CONTAINER_NAME=ci_native_fuzz_valgrind`
build: use header-only Boost unit test 2022-02-09 18:15:10 +00:00			`export PACKAGES="clang llvm python3 libevent-dev bsdmainutils libboost-dev libsqlite3-dev valgrind"`
ci: Run fuzz testing test cases under valgrind 2020-02-17 13:34:51 +00:00			`export NO_DEPENDS=1`
			`export RUN_UNIT_TESTS=false`
			`export RUN_FUNCTIONAL_TESTS=false`
			`export RUN_FUZZ_TESTS=true`
util: Avoid potential uninitialized read in FormatISO8601DateTime(int64_t nTime) by checking gmtime_s/gmtime_r return value 2020-02-16 11:28:37 +00:00			`export FUZZ_TESTS_CONFIG="--valgrind"`
ci: Run fuzz testing test cases under valgrind 2020-02-17 13:34:51 +00:00			`export GOAL="install"`
ci: use DWARF-4 for Valgrind CI job clang-14 defaults to using DWARF-5, which breaks vlagrinds (3.18) ability to parse debug info. Valgrind claims to support DWARF-5 from version 3.18 onwards, but maybe that only works when building with GCC. Explicitly use DWARF-4 for now. Note that from 11.0 GCC also defaults to using DWARF-5. https://releases.llvm.org/14.0.0/tools/clang/docs/ReleaseNotes.html#dwarf-support-in-clang https://www.gnu.org/software/gcc/gcc-11/changes.html https://valgrind.org/docs/manual/dist.news.html 2022-04-01 12:57:40 +01:00			`# Temporarily pin dwarf 4, until valgrind can understand clang's dwarf 5`
ci: better pin to dwarf4 in valgrind job Use `-gdwarf` and also set CFLAGS. I was seeing Valgrind issues otherwise. 2022-07-20 09:11:15 +01:00			`export BITCOIN_CONFIG="--enable-fuzz --with-sanitizers=fuzzer CC=clang CXX=clang++ CFLAGS='-gdwarf-4' CXXFLAGS='-gdwarf-4'"`
ci: Increase CCACHE_SIZE in some builds on Travis 2020-07-14 19:00:49 +03:00			`export CCACHE_SIZE=200M`