the malloc debug system assumes single thread

diff --git a/lib/README.memoryleak b/lib/README.memoryleak
index 8402dc40ed85084f2e22255c656071e49bfc91e6..8fe2db78a55a34eb74978e69f5c756a4d8958a13 100644 (file)
--- a/lib/README.memoryleak
+++ b/lib/README.memoryleak
@@ -8,6 +8,13 @@ $Id$
              How To Track Down Suspected Memory Leaks in libcurl
              ===================================================
 
+Single-threaded
+
+  Please note that this memory leak system is not adjusted to work in more
+  than one thread. If you want/need to use it in a multi-threaded app. Please
+  adjust accordingly.
+
+
 Build
 
   Rebuild libcurl with -DMALLOCDEBUG (usually, rerunning configure with