Hi Fu, Don't worry there is no problem at all. Actually, the instructions for a single instance (c9-worker) of Cloud9 is for ensuring that the program has been installed correctly and it runs without crashing so the code coverage is not important. The instructions for running Cloud9 on a Cluster let you configure a script that will manage several instances (c9-worker) of Cloud9 across one or several nodes. However, if you still want to run a stand-alone single instance of Cloud9 and track the code coverage you just need to specify a file that tells Cloud9 where the .c file of the code it is testing is. We have created one for the binutils binaries, so following the example in the instructions you just need to run the following command:
./c9-worker --stand-alone --posix-runtime --libc=uclibc -coverable-modules=[The 'cloud9/infra' path]/coverable/coreutils.coverable .[The 'cloud9/targets' path]/src/printf.bc --sym-args 0 2 5 Regards, Javier ________________________________________ From: Fu Bin-zhang [[email protected]] Sent: 01 April 2012 04:32 To: [email protected] Subject: A question about "software testing" Hi all, I am tring to use the cloudsuite to evaluate our platform. When i tried the software testing with "Single Node" mode, I found that the code coverage was always 0/0 as shown in the following. I think there might be some problems, but the compiler did not report any error. Any hint is appreciated. Thanks in advance. ---------------------output example-------------------------------- ... [91367.304] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global).. [92050.819] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global).. ... -------------------------------------------------------------------- Best Regards, Fbz.
