Don't add potentially nasty stderr uses to dead CRYPTO_dbg_mem functions.

But do use the abort(), which we are hoping all future vendors will move
towards the more modern "do not flush streams"; hint hint, if you didn't
do that already, there are grave risks because much software brings risk
without that behaviour. We didn't cause the change.. POSIX did...
ok beck

1 files changed, 3 insertions, 3 deletions

diff --git a/lib/libcrypto/mem_dbg.c b/lib/libcrypto/mem_dbg.c
index 288ee907c34..3e56c79a25a 100644
--- a/lib/libcrypto/mem_dbg.c
+++ b/lib/libcrypto/mem_dbg.c
@@ -162,14 +162,14 @@ void
 CRYPTO_dbg_malloc(void *addr, int num, const char *file, int line,
     int before_p)
 {
-	fprintf(stderr, "this is a bad idea");
+	/* CRYPTO_dbg_malloc is no longer permitted */
 	abort();
 }
 
 void
 CRYPTO_dbg_free(void *addr, int before_p)
 {
-	fprintf(stderr, "this is a bad idea");
+	/* CRYPTO_dbg_free is no longer permitted */
 	abort();
 }
 
@@ -177,7 +177,7 @@ void
 CRYPTO_dbg_realloc(void *addr1, void *addr2, int num,
     const char *file, int line, int before_p)
 {
-	fprintf(stderr, "this is a bad idea");
+	/* CRYPTO_dbg_realloc is no longer permitted */
 	abort();
 }