[or-cvs] r11217: remove spaces at end of lines (topf/trunk/doc)

[arma@xxxxxxxx]

Author: arma
Date: 2007-08-20 11:42:27 -0400 (Mon, 20 Aug 2007)
New Revision: 11217

Modified:
   topf/trunk/doc/tutorial.tex
Log:
remove spaces at end of lines


Modified: topf/trunk/doc/tutorial.tex
===================================================================
--- topf/trunk/doc/tutorial.tex	2007-08-20 14:59:08 UTC (rev 11216)
+++ topf/trunk/doc/tutorial.tex	2007-08-20 15:42:27 UTC (rev 11217)
@@ -40,8 +40,8 @@
 
 \subsection{Running the fuzz tests}
 \subsubsection{Adjusting the config File}
-To let the Framework work properly the right setup of the 
-config-file is nessesary. Just alter the given options 
+To let the Framework work properly the right setup of the
+config-file is nessesary. Just alter the given options
 to your environment.
 
 \begin{verbatim}
@@ -57,17 +57,17 @@
 
 \subsubsection{Setting the u-limit}
 To let your system create core-dumps you normaly have
-to adjust your ulimit. You can do this on the 
+to adjust your ulimit. You can do this on the
 shell with the command: "ulimit -c unlimited"
 \subsubsection{Setting a core-pattern}
-T.O.P.F checks if a process has been crashed by diffing the 
+T.O.P.F checks if a process has been crashed by diffing the
 coredump-directory that was setup in the config-file.
-To let your system create core-files in this directory you 
+To let your system create core-files in this directory you
 have to supply a core-pattern. If you work with Linux you
-can set the core-pattern with echoing a path+filepattern 
+can set the core-pattern with echoing a path+filepattern
 into the file in proc named core\_pattern.
 When using Fedora this can be done with the following command
- executed as root: 
+ executed as root:
  \begin{verbatim}
  echo "/home/youruser/path_to_topf/core/core" > /proc/sys/kernel/core_pattern
  \end{verbatim}
@@ -77,7 +77,7 @@
 the right host and dir-port in the configuration file.
 If everything is setup right you can just execute the dir-fuzzing
 with the command "ruby tor-dir-fuzz.rb".
-If something goes wrong a corefile should be dumped and the 
+If something goes wrong a corefile should be dumped and the
 test-script should give you a backtrace and register information
 out of that corefile. Also it should print out the data that triggered
 the bug.
@@ -110,12 +110,12 @@
     pp e
 end
 \end{verbatim}
-This creates a Class called "Example" with the fields of a 8*8Bit long String, 
-a 8Bit unsigned integer. and the initial values "example" and 1 for these. 
-Also the Text-Field is declared as not fuzzable which means that later the 
-value assigned to it remains the same. Next in the begin/end block the 
-programm creates a Example object and sets the value of the version field to 2. 
-This also demonstrates how you are able to access all fields after you created 
+This creates a Class called "Example" with the fields of a 8*8Bit long String,
+a 8Bit unsigned integer. and the initial values "example" and 1 for these.
+Also the Text-Field is declared as not fuzzable which means that later the
+value assigned to it remains the same. Next in the begin/end block the
+programm creates a Example object and sets the value of the version field to 2.
+This also demonstrates how you are able to access all fields after you created
 a fuzz-struct object.
 
 
@@ -129,10 +129,10 @@
 \begin{verbatim}
     a_test = Fuzz::Test.new("char") {|arg, size|  "A"*1000}
 \end{verbatim}
-To apply this test to a fuzz-struct you actually need another object which 
-acts as a collector for many tests. This object is called Fuzz::Tests and 
-is later applied to a fuzz-struct. The next example shows how you write some 
-tests, assign them to the collector object and apply all tests to a structure 
+To apply this test to a fuzz-struct you actually need another object which
+acts as a collector for many tests. This object is called Fuzz::Tests and
+is later applied to a fuzz-struct. The next example shows how you write some
+tests, assign them to the collector object and apply all tests to a structure
 and output all permutations calculateable through these tests.
 
 \begin{verbatim}
@@ -157,9 +157,9 @@
 
     # tests for unsigned numbers
     example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  arg } # return argument
-    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  0 } # return zero 
-    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  rand(5) } # return a small number 
-    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  2.power!(size) } # return biggest number 
+    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  0 } # return zero
+    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  rand(5) } # return a small number
+    example_tests.register Fuzz::Test.new("unsigned") {|arg, size|  2.power!(size) } # return biggest number
 
     e = Example.new
     e.prepare! example_tests