From 18c0ad336d516f5c101e025f2ae40a7d941c5456 Mon Sep 17 00:00:00 2001 From: Luis Franca Date: Sun, 30 Apr 2017 15:49:25 -0300 Subject: [PATCH] Fixing typos and gdb command line in DEVELOPING.md --- doc/readme/DEVELOPING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/readme/DEVELOPING.md b/doc/readme/DEVELOPING.md index d9b684f8de7..a6b85ba5e98 100644 --- a/doc/readme/DEVELOPING.md +++ b/doc/readme/DEVELOPING.md @@ -127,7 +127,7 @@ You can execute single tests via `ctest`, or via directly executing the unit tes Note that wildcards are allowed. Running single sub-tests is sometimes useful (i.e. for bug hunting) - ./bin/shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_apply_regression + ./bin/shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_regression ### Debugging and Memory leaks **All your C++ code and unit tests must be checked to not leak memory!** @@ -136,8 +136,8 @@ If you do that, you might want to compile with debugging symbols and without com Then - valgrind ./shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_apply_regression - gdb ./shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_apply_regression + valgrind ./bin/shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_regression + gdb --args ./bin/shogun-unit-test --gtest_filter=GaussianProcessRegression.apply_regression The option `--leak-check=full` for valgrind might be useful. In addition to manually running valgrind on your tests, you can use `ctest` to check multiple tests.