From 8f8e211e006b64eece2276993677db56db98ff54 Mon Sep 17 00:00:00 2001 From: Cristian Cadar Date: Fri, 11 Jan 2013 09:27:33 +0000 Subject: Improved a bit the documentation for testing Coreutils. Thanks to Tomasz Kuchta for his help. git-svn-id: https://llvm.org/svn/llvm-project/klee/trunk@172186 91177308-0d34-0410-b5e6-96231b3b80d8 --- www/TestingCoreutils.html | 34 ++++++++++++++++++++-------------- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git a/www/TestingCoreutils.html b/www/TestingCoreutils.html index 3465382f..7ae49302 100644 --- a/www/TestingCoreutils.html +++ b/www/TestingCoreutils.html @@ -17,15 +17,22 @@

As a more detailed explanation of using KLEE, we will look at how we did our testing of GNU - coreutils using KLEE. + Coreutils using KLEE.

-

- These tests were done on a 32-bit Intel Linux machine, they aren't likely to - work elsewhere. In addition, you will need to have configured and built KLEE +

This tutorial assumes that you have configured and built KLEE with uclibc and POSIX runtime support. -

+

+

These tests were done on a 32-bit Linux machine. On a 64-bit + machine, we needed to also set the LD_LIBRARY_PATH environment + variable: +

+    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64 (Fedora)
+    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/x86_64-linux-gnu (Ubuntu)
+    
+

+

Step 1: Build coreutils with gcov

@@ -56,6 +63,7 @@ obj-gcov$ ../configure --disable-nls CFLAGS="-g -fprofile-arcs -ftest-coverage" ... verify that configure worked ... obj-gcov$ make +obj-gcov$ make -C src arch hostname ... verify that make worked ... @@ -170,6 +178,7 @@ Lines executed:18.81% of 101 obj-llvm$ ../configure --disable-nls CFLAGS="-g" ... verify that configure worked ... obj-llvm$ make CC=/full/path/to/klee/scripts/klee-gcc +obj-llvm$ make -C src arch hostname CC=/full/path/to/klee/scripts/klee-gcc ... verify that make worked ... @@ -871,16 +880,13 @@ Lines executed:97.03% of 101

- -

Step 7: Running KLEE on larger applications

- - To be written. - - - -

Step 8: Using zcov to analyze coverage

+ +

Step 7: Using zcov to analyze coverage

- To be written. +

+ For visualizing the coverage results, you might want to use the zcov tool. +

+
-- cgit 1.4.1