diff options
| author | Nick Mathewson <nickm@torproject.org> | 2012-10-24 15:03:49 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2012-10-24 15:03:49 -0400 |
| commit | 4a9bc5658f4d7fa786aa2a154bba00f4e3f0bc45 (patch) | |
| tree | 4b4bcb4b13aaa1e6ff39dc9f15ebae55c4854a60 /doc/HACKING | |
| parent | 3d825d22c3d20f03b34cbe4d9e8874a816e45c4a (diff) | |
| download | tor-4a9bc5658f4d7fa786aa2a154bba00f4e3f0bc45.tar.gz tor-4a9bc5658f4d7fa786aa2a154bba00f4e3f0bc45.zip | |
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.
Diffstat (limited to 'doc/HACKING')
| -rw-r--r-- | doc/HACKING | 10 |
1 files changed, 9 insertions, 1 deletions
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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |