[tor-commits] [tor/master] Fix instructions for using Tor with gcov

nickm at torproject.org nickm at torproject.org
Wed Oct 24 19:04:30 UTC 2012

commit 4a9bc5658f4d7fa786aa2a154bba00f4e3f0bc45
Author: Nick Mathewson <nickm at torproject.org>
Date:   Wed Oct 24 15:03:49 2012 -0400

    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.
 doc/HACKING |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/doc/HACKING b/doc/HACKING
index e76b374..c06a682 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'
-  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

More information about the tor-commits mailing list