From 895f53d1cf9719f34b5248afe6aab33deeb8e26c Mon Sep 17 00:00:00 2001 From: Tim Ruffing Date: Wed, 20 Aug 2025 09:57:10 +0200 Subject: [PATCH] docs: Clarify that callback can be called more than once --- include/secp256k1.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/secp256k1.h b/include/secp256k1.h index f55a6ab9..ae31ff70 100644 --- a/include/secp256k1.h +++ b/include/secp256k1.h @@ -340,9 +340,9 @@ SECP256K1_API void secp256k1_context_destroy( * * On the other hand, during debug stage, one would want to be informed about * such mistakes, and the default (crashing) may be inadvisable. - * When this callback is triggered, the API function called is guaranteed not - * to cause a crash, though its return value and output arguments are - * undefined. + * Should this callback return instead of crashing, the return value and output + * arguments of the API function call are undefined. Moreover, the same API + * call may trigger the callback again in this case. * * When this function has not been called (or called with fn==NULL), then the * default handler will be used. The library provides a default handler which