[tor-commits] [tor/master] Remove trailing whitespace

[nickm at torproject.org]

commit c93428f457273189d8f5ea3ff3e4f1d7fe6ba6d2
Author: Nick Mathewson <nickm at torproject.org>
Date:   Fri Jan 13 12:31:06 2017 -0500

    Remove trailing whitespace
---
 doc/HACKING/HelpfulTools.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/HACKING/HelpfulTools.md b/doc/HACKING/HelpfulTools.md
index 8e9051d..67481ac 100644
--- a/doc/HACKING/HelpfulTools.md
+++ b/doc/HACKING/HelpfulTools.md
@@ -173,25 +173,25 @@ Here are some basic instructions
    * `opcontrol --dump;`
    * `opreport -l that_dir/*`
  - Profit
- 
+
 Profiling Tor with perf
 -----------------------
 
 This works with a running Tor, and requires root.
- 
+
 1. Decide how long you want to profile for. Start with (say) 30 seconds. If that
    works, try again with longer times.
 
 2. Find the PID of your running tor process.
 
 3. Run `perf record --call-graph dwarf -p <PID> sleep <SECONDS>`
-    
+
    (You may need to do this as root.)
-      
+
    You might need to add `-e cpu-clock` as an option to the perf record line
    above, if you are on an older CPU without access to hardware profiling
    events, or in a VM, or something.
-   
+
 4. Now you have a perf.data file. Have a look at it with `perf report
    --no-children --sort symbol,dso` or `perf report --no-children --sort
    symbol,dso --stdio --header`. How does it look?
@@ -220,7 +220,7 @@ performance! See the gperftools manual for more info, but basically:
 
 2. Run `env CPUPROFILE=/tmp/profile src/or/tor -f <path/torrc>`. The profile file
    is not written to until Tor finishes execuction.
-   
+
 3. Run `pprof src/or/tor /tm/profile` to start the REPL.
 
 Generating and analyzing a callgraph