From 5a40295c4cf0af5ea8da9ced04a4ce7d3621a080 Mon Sep 17 00:00:00 2001 From: Toni Uhlig Date: Sun, 16 Jul 2023 02:03:33 +0200 Subject: Squashed 'flatcc/' content from commit 473da2a git-subtree-dir: flatcc git-subtree-split: 473da2afa5ca435363f8c5e6569167aee6bc31c5 --- test/README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 test/README.md (limited to 'test/README.md') diff --git a/test/README.md b/test/README.md new file mode 100644 index 0000000..4c0b485 --- /dev/null +++ b/test/README.md @@ -0,0 +1,19 @@ +NOTE: shell scripts driven by flatcc/test/test.sh have been ported to CMake. +use flatcc/scripts/test.sh to drive CMake tests. + +Run `leakcheck.sh` and `leakcheck-full.sh` for memory checks. + +To install valgrind on OS-X Yosemite use `brew install --HEAD valgrind` + +For decoding valgrind error messages: + + +clang has built-in memory check, but only for `x86_64 Linux`: + + +On OS-X Yosemite with valgrind that isn't officially supported for that +platform, a few spurious unitialized memory access errors are reported +when printing the filextension in `codegen_c.c`. and in the equivalent +builder. After inspection, nothing suggests this is an actual bug - more +likely it relates to a strnlen optimization in fprintf `"%.*s"` syntax +that valgrind doesn't catch. -- cgit v1.2.3