From: Nick Mathewson <nickm@torproject.org>
Date: Wed, 24 Oct 2012 19:03:49 +0000 (-0400)
Subject: Fix instructions for using Tor with gcov
X-Git-Tag: tor-0.2.4.5-alpha~11
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=4a9bc5658f4d7fa786aa2a154bba00f4e3f0bc45;p=thirdparty%2Ftor.git

Fix instructions for using Tor with gcov

It seems as if our new build system broke gcov for me.  I've tried to
fix doc/HACKING to describe what I needed to do in order to make it
work again.
---

diff --git a/doc/HACKING b/doc/HACKING
index e76b374d30..c06a682683 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -121,7 +121,8 @@ Running gcov for unit test coverage
   make clean
   make CFLAGS='-g -fprofile-arcs -ftest-coverage'
   ./src/test/test
-  cd src/common; gcov *.[ch]
+  gcov -o src/common src/common/*.[ch]
+  gcov -o src/or src/or/*.[ch]
   cd ../or; gcov *.[ch]
 -----
 
@@ -130,6 +131,13 @@ compiler generated  no code for that line.  '######' means that the
 line was never reached.  Lines with numbers were called that number
 of times.
 
+If that doesn't work:
+   * Try configuring Tor with --disable-gcc-hardening
+   * On recent OSX versions, you might need to add CC=clang to your
+     build line, as in:
+        make CFLAGS='-g -fprofile-arcs -ftest-coverage' CC=clang
+     Their llvm-gcc doesn't work so great for me.
+
 Profiling Tor with oprofile
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~