test: show both Autotools and CMake usage for ctime_tests
What the developer wrote
Authored by 8144225309
test: show both Autotools and CMake usage for ctime_tests
The existing message only shows the libtool command, which is
specific to Autotools builds.
Fixes #1697
What changed, and why it matters
This commit only changes the wording of an error/help message in a test program. It tells users how to run a test under valgrind for both CMake and Autotools builds. There is no security issue here.
No action needed; this is a documentation-only test change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies a single fprintf() line in src/ctime_tests.c. The old message only documented the Autotools/libtool invocation; the new message documents both the direct CMake-style usage and the Autotools usage. No code logic, cryptographic operations, memory handling, or build configuration changed.
Changed components
src/ctime_tests.c (test-only error message)Inspect captured patch +1 / −1
diff --git a/src/ctime_tests.c b/src/ctime_tests.c
index f81bdb9..f80042a 100644
--- a/src/ctime_tests.c
+++ b/src/ctime_tests.c
@@ -49,7 +49,7 @@ int main(void) {
if (!SECP256K1_CHECKMEM_RUNNING()) {
fprintf(stderr, "This test can only usefully be run inside valgrind because it was not compiled under msan.\n");
- fprintf(stderr, "Usage: libtool --mode=execute valgrind ./ctime_tests\n");
+ fprintf(stderr, "Usage: valgrind ./ctime_tests (or with Autotools: libtool --mode=execute valgrind ./ctime_tests)\n");
return EXIT_FAILURE;
}
ctx = secp256k1_context_create(SECP256K1_CONTEXT_DECLASSIFY);
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.