From: Yang Tse <yangsita@gmail.com>
Date: Fri, 12 Jun 2009 23:51:28 +0000 (+0000)
Subject: Try to make more clear that --enable-curldebug has nothing to do with --enable-debug... 
X-Git-Tag: curl-7_19_6~125
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=067544abc586e04568c8e9026a09005187029b66;p=curl

Try to make more clear that --enable-curldebug has nothing to do with --enable-debug for this library.
---

diff --git a/ares/CHANGES b/ares/CHANGES
index 04bea6c53..f98105f32 100644
--- a/ares/CHANGES
+++ b/ares/CHANGES
@@ -10,6 +10,16 @@
   setting from --enable-debug, allowing again to build c-ares independently
   out of the CVS tree.
 
+  For the c-ares library option --enable-debug enables debug build features
+  which are _not_ related with memory tracking. For the c-ares library when
+  --enable-debug is given it does not enable the memory tracking feature. If
+  you wish to enable the curl debug memory tracking you must use configure
+  option --enable-curldebug explicitily to do so.
+
+  Internally, definition of preprocessor symbol DEBUGBUILD restricts code
+  which is only compiled for debug enabled builds. And symbol CURLDEBUG is
+  used to differentiate code which is _only_ used for memory tracking.
+
 * May 19 2009 (Yang Tse)
 - Introduced ares_library_init() and ares_library_cleanup() functions.