From: Nick Mathewson <nickm@torproject.org>
Date: Tue, 19 May 2009 14:40:20 +0000 (-0400)
Subject: Clearer valgrind instructions for non-Debian openssls
X-Git-Tag: tor-0.2.2.1-alpha~134
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7d84b84608f7425208e60020dcede1561e53a170;p=thirdparty%2Ftor.git

Clearer valgrind instructions for non-Debian openssls
---

diff --git a/doc/HACKING b/doc/HACKING
index 50b5d80d18..3d3f2c1dfc 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -11,12 +11,20 @@
 0.1. Useful command-lines that are non-trivial to reproduce but can
 help with tracking bugs or leaks.
 
+0.1.1. Dmalloc
+
 dmalloc -l ~/dmalloc.log
 (run the commands it tells you)
 ./configure --with-dmalloc
 
+0.2.2. Valgrind
+
 valgrind --leak-check=yes --error-limit=no --show-reachable=yes src/or/tor
 
+(Note that if you get a zillion openssl warnings, you will also need to
+ pass --undef-value-errors=no to valgrind, or rebuild your openssl
+ with -DPURIFY.)
+
 0.2. Running gcov for unit test coverage
 
   make clean