summaryrefslogtreecommitdiff
path: root/docs/README-gcov_for_udev
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@vrfy.org>2008-06-26 18:12:50 +0200
committerKay Sievers <kay.sievers@vrfy.org>2008-06-26 18:12:50 +0200
commit8bf875ff282e683e80849113c87660c7b2a0e772 (patch)
treec17b83f200572ba2038f91cf8285c2fec4d27acb /docs/README-gcov_for_udev
parentec9611ddb50eba7e38a77372ff1d5137f491144a (diff)
docs: update some docs and delete outdated stuff
Diffstat (limited to 'docs/README-gcov_for_udev')
-rw-r--r--docs/README-gcov_for_udev34
1 files changed, 6 insertions, 28 deletions
diff --git a/docs/README-gcov_for_udev b/docs/README-gcov_for_udev
index c223dc38e8..5acb53a27c 100644
--- a/docs/README-gcov_for_udev
+++ b/docs/README-gcov_for_udev
@@ -14,37 +14,19 @@ With that said, here is how to get code coverage analysis for udev files.
Note that this was developed with udev version 024.
- Make sure you've installed udev and that it is working properly.
- If you are having problems, refer to the README and HOWTO-udev_for_dev
- documents in udev tarball.
-
-- execute make_gcov.sh from udev top level directory
+- Build udev with:
make gcov-all
-
- This will compile udev with gcov support. Basically make_gcov.sh will
- run make but override the CFLAGS. It strips any optimization from
- CFLAGS in order for gcov to get correct code coverage analysis. It will
- also add the -fprofile-arcs and -ftest-coverage options which are the
- necessary flags needed to use gcov.
-
- If you look into your udev directory and see that it has been polluted with
- a bunch of *.gcno, *.gcda and *.gcov files. gcov creates and uses these files
- to extract the code coverage info.
-
-- After running make_gcov.sh you need to install udev again. So basically,
-
- su to root
- make install
+ This will compile udev with gcov support. If you look into your udev directory
+ and see that it has been polluted with a bunch of *.gcno, *.gcda and *.gcov files.
+ gcov creates and uses these files to extract the code coverage info.
- Then execute some udev tasks. You can run some udev tests, reboot, or
do anything your little udev heart desires. Once you are satisfied, you
can now see how much udev code was covered. I personally recommend just
running test/udev-test.pl for starters.
-- To get the udev code coverage analysis, execute run_gcov.sh from udev top
- level directory. You need to be root to do this.
-
- su to root
+- To get the udev code coverage analysis:
make udev_gcov.txt
- This creates udev_gcov.txt in the udev top level directory which holds all
@@ -83,8 +65,4 @@ Note that this was developed with udev version 024.
- Once you are done with using gcov for udev and want to return to your
normal use of udev, run a regular 'make clean' on your udev directory.
- Then just run a regular make and make install and you are back to normal:
-
- make clean all
- su to root
- make install
+ Then just run a regular make and make install and you are back to normal.