From ef32afca0934a1c5c00a21b0be36ca499d263e58 Mon Sep 17 00:00:00 2001 From: DL6ER Date: Fri, 15 Nov 2024 18:41:06 +0100 Subject: [PATCH] Add note that FTL will run much slower in valgrind Signed-off-by: DL6ER --- docs/ftldns/valgrind.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ftldns/valgrind.md b/docs/ftldns/valgrind.md index 94c1e75b9..42b597277 100644 --- a/docs/ftldns/valgrind.md +++ b/docs/ftldns/valgrind.md @@ -2,7 +2,7 @@ Occasionally, debugging may require us to run `pihole-FTL` in `valgrind`. We also use it to measure performance and check that our memory layout is optimal (= minimal footprint). -`Valgrind` is a flexible program for debugging and profiling Linux executables. It consists of a core, which provides a synthetic CPU in software, and a series of debugging and profiling tools. +`Valgrind` is a flexible program for debugging and profiling Linux executables. It consists of a core, which provides a synthetic CPU in software, and a series of debugging and profiling tools. The use of a synthetic CPU allows Valgrind to run the client program in a completely controlled environment and, hence, track the behaviour of the program in a very detailed way. Unfortunately, this also means that the program runs *much* slower than usual. ## `memcheck`