summaryrefslogtreecommitdiff
path: root/board/sandbox
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2019-05-18 11:59:50 -0600
committerSimon Glass <sjg@chromium.org>2019-07-10 16:52:58 -0600
commit80b7cb8c3230bb29b065633c803694d8720ecadf (patch)
tree11a4f20dae2a76f2e6bb4deb4847c55855a3605c /board/sandbox
parent24c2776ba9002fadbf7cf86a0f5bc6a17cc08290 (diff)
downloadu-boot-80b7cb8c3230bb29b065633c803694d8720ecadf.tar.gz
sandbox: Add documentation on how to run valgrind
U-Boot sandbox can run with valgrind to check memory allocations. Add documentation on how to do this. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'board/sandbox')
-rw-r--r--board/sandbox/README.sandbox14
1 files changed, 14 insertions, 0 deletions
diff --git a/board/sandbox/README.sandbox b/board/sandbox/README.sandbox
index 5e8fa58ba2..c10dd444df 100644
--- a/board/sandbox/README.sandbox
+++ b/board/sandbox/README.sandbox
@@ -442,6 +442,20 @@ If sdl-config is on a different path from the default, set the SDL_CONFIG
environment variable to the correct pathname before building U-Boot.
+Using valgrind / memcheck
+-------------------------
+
+It is possible to run U-Boot under valgrind to check memory allocations:
+
+ valgrind u-boot
+
+If you are running sandbox SPL or TPL, then valgrind will not by default
+notice when U-Boot jumps from TPL to SPL, or from SPL to U-Boot proper. To
+fix this, use:
+
+ valgrind --trace-children=yes u-boot
+
+
Testing
-------