Re: MemoryTracking internal adjustments
Date: Wed, 17 Aug 2011 14:47:08 +0200
Attached patch (comments inside) takes in consideration the
possibility that someone might still want old behavior.
Given that this only affects debug builds with TrackMemory feature
enabled, and default option should be disabled, I'm a bit reluctant to
allow setting CURL_MT_MALLOC_FILL and CURL_MT_FREE_FILL via configure
script. But I'm not fully against it, if the need actually exists.
Don't really know if your concerns were mostly related with embedded
systems or with the torture tests autobuild. In any case... Fix for
memdebug.c good enough now?
- application/octet-stream attachment: memdebug.patch.take2