From 483262b2a2d0ed2f348b3722e8cf78994bc6023c Mon Sep 17 00:00:00 2001 From: Harry Ramsey Date: Tue, 18 Feb 2025 22:23:48 +0000 Subject: [PATCH] Update comments regarding the zeroize program This commit updates comments regarding the moved zeroize files. Signed-off-by: Harry Ramsey --- tests/programs/test_zeroize.gdb | 2 +- tests/programs/zeroize.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/programs/test_zeroize.gdb b/tests/programs/test_zeroize.gdb index f8f0ac4b0..6eaf61ba6 100644 --- a/tests/programs/test_zeroize.gdb +++ b/tests/programs/test_zeroize.gdb @@ -7,7 +7,7 @@ # # Run a test using the debugger to check that the mbedtls_platform_zeroize() # function in platform_util.h is not being optimized out by the compiler. To do -# so, the script loads the test program at programs/test/zeroize.c and sets a +# so, the script loads the test program at programs/test/zeroize and sets a # breakpoint at the last return statement in main(). When the breakpoint is # hit, the debugger manually checks the contents to be zeroized and checks that # it is actually cleared. diff --git a/tests/programs/zeroize.c b/tests/programs/zeroize.c index c1cee0d84..d81358e81 100644 --- a/tests/programs/zeroize.c +++ b/tests/programs/zeroize.c @@ -4,7 +4,7 @@ * This is a simple test application used for debugger-driven testing to check * whether calls to mbedtls_platform_zeroize() are being eliminated by compiler * optimizations. This application is used by the GDB script at - * tests/scripts/test_zeroize.gdb: the script sets a breakpoint at the last + * tests/programs/test_zeroize.gdb: the script sets a breakpoint at the last * return statement in the main() function of this program. The debugger * facilities are then used to manually inspect the memory and verify that the * call to mbedtls_platform_zeroize() was not eliminated.