From 58b2a48b3feafc956874e023785b421c920229f5 Mon Sep 17 00:00:00 2001 From: Kevin Day Date: Sun, 20 Feb 2022 00:40:06 -0600 Subject: [PATCH] Update: Add additional debugging documentation notes. --- documents/debugging.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/documents/debugging.txt b/documents/debugging.txt index dd6d5d4..182c985 100644 --- a/documents/debugging.txt +++ b/documents/debugging.txt @@ -41,6 +41,11 @@ Valgrind: The "valkyrie" program does not support massif at the time of this writing but it eventually may. The "valkyrie" program does support the default valgrind tool and the helgrind tools. + When working with valgrind's massif tool, several libc functions (or other functions external to this project) may get in the way of the analysis. + These functions should be disabled. + Example valgrind massif execution disabling some common GLibc functions: + valgrind --tool=massif --ignore-fn=_IO_file_doallocate --ignore-fn=ftw_startup --ignore-fn=__alloc_dir fake clean build + GCC's -fanalyzer (and CLang's equivalent): The code analyzer provided by GCC (and also CLang, through similar means) attempts to determine insecure or otherwise bad coding practices. -- 1.8.3.1