nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-10 13:13:44 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix instructions for using Tor with gcov

Browse Source 
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.
This commit is contained in:
Nick Mathewson 2012-10-24 15:03:49 -04:00
parent 3d825d22c3
commit 4a9bc5658f
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/HACKING
View File

@ -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
~~~~~~~~~~~~~~~~~~~~~~~~~~~