From 0ff0a994ada62aa1f34c8f729b9ef2ded9b0e2a9 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 25 Dec 2013 00:53:15 +0100 Subject: [PATCH] Curl_thread_create: use Curl_safefree to allow NULL better free() itself allows a NULL input but our memory debug system requires Curl_safefree() to be used instead when a "legitimate" NULL may be freed. Like in the code here. Pointed-out-by: Steve Holme --- lib/curl_threads.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/curl_threads.c b/lib/curl_threads.c index 97527807e..d40e024c8 100644 --- a/lib/curl_threads.c +++ b/lib/curl_threads.c @@ -77,8 +77,8 @@ curl_thread_t Curl_thread_create(unsigned int (*func) (void*), void *arg) return t; err: - free(t); - free(ac); + Curl_safefree(t); + Curl_safefree(ac); return curl_thread_t_null; }