summaryrefslogtreecommitdiff
path: root/lib/README.memoryleak
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2002-10-28 21:05:14 +0000
committerDaniel Stenberg <daniel@haxx.se>2002-10-28 21:05:14 +0000
commit8f52b731f45eabd5b036b146a27e93ec7fa9e807 (patch)
tree5659e6b333d23e65dc6b90b4342c7464906d9ac8 /lib/README.memoryleak
parentd442088ed38cf11e56e848523e1fa60c2697e856 (diff)
downloadcurl-8f52b731f45eabd5b036b146a27e93ec7fa9e807.tar.gz
the malloc debug system assumes single thread
Diffstat (limited to 'lib/README.memoryleak')
-rw-r--r--lib/README.memoryleak7
1 files changed, 7 insertions, 0 deletions
diff --git a/lib/README.memoryleak b/lib/README.memoryleak
index 8402dc40e..8fe2db78a 100644
--- 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