[Valgrind-developers] valgrind

[Nicholas N. <nj...@ca...>]

CVS commit by nethercote: 

 
Streamlined --help message a bit.


  M +7 -12     coregrind/vg_main.c   1.157
  M +7 -12     none/tests/cmdline1.stdout.exp   1.5
  M +7 -12     none/tests/cmdline2.stdout.exp   1.5


--- valgrind/coregrind/vg_main.c  #1.156:1.157
@@ -1509,5 +1509,5 @@ void usage ( Bool debug_help )
 "\n"
 "  common user options for all Valgrind tools, with defaults in [ ]:\n"
-"    --tool=<name>             Use the Valgrind tool named <name>\n"
+"    --tool=<name>             use the Valgrind tool named <name>\n"
 "    -h --help                 show this message\n"
 "    --help-debug              show this message, plus debugging options\n"
@@ -1516,17 +1516,12 @@ void usage ( Bool debug_help )
 "    -v --verbose              be more verbose, incl counts of errors\n"
 "    --trace-children=no|yes   Valgrind-ise child processes? [no]\n"
-"    --track-fds=no|yes        Track open file descriptors? [no]\n"
+"    --track-fds=no|yes        track open file descriptors? [no]\n"
 "\n"
 "  uncommon user options for all Valgrind tools:\n"
-"    --run-libc-freeres=no|yes Free up glibc memory at exit? [yes]\n"
-"    --weird-hacks=hack1,hack2,...  [none]\n"
-"         recognised hacks are: lax-ioctls\n"
-"    --signal-polltime=<time>  time, in mS, we should poll for signals.\n"
-"                              Only applies for older kernels which need\n"
-"                              signal routing [50]\n"
-"    --lowlat-signals=no|yes   improve wake-up latency when a thread receives\n"
-"                              a signal [no]\n"
-"    --lowlat-syscalls=no|yes  improve wake-up latency when a thread's\n"
-"                              syscall completes [no]\n"
+"    --run-libc-freeres=no|yes free up glibc memory at exit? [yes]\n"
+"    --weird-hacks=hack1,hack2,...  recognised hacks: lax-ioctls [none]\n"
+"    --signal-polltime=<time>  signal poll period (mS) for older kernels [50]\n"
+"    --lowlat-signals=no|yes   improve thread signal wake-up latency [no]\n"
+"    --lowlat-syscalls=no|yes  improve thread syscall wake-up latency [no]\n"
 "    --pointercheck=no|yes     enforce client address space limits [yes]\n"
 "\n"

--- valgrind/none/tests/cmdline1.stdout.exp  #1.4:1.5
@@ -2,5 +2,5 @@
 
   common user options for all Valgrind tools, with defaults in [ ]:
-    --tool=<name>             Use the Valgrind tool named <name>
+    --tool=<name>             use the Valgrind tool named <name>
     -h --help                 show this message
     --help-debug              show this message, plus debugging options
@@ -9,17 +9,12 @@
     -v --verbose              be more verbose, incl counts of errors
     --trace-children=no|yes   Valgrind-ise child processes? [no]
-    --track-fds=no|yes        Track open file descriptors? [no]
+    --track-fds=no|yes        track open file descriptors? [no]
 
   uncommon user options for all Valgrind tools:
-    --run-libc-freeres=no|yes Free up glibc memory at exit? [yes]
-    --weird-hacks=hack1,hack2,...  [none]
-         recognised hacks are: lax-ioctls
-    --signal-polltime=<time>  time, in mS, we should poll for signals.
-                              Only applies for older kernels which need
-                              signal routing [50]
-    --lowlat-signals=no|yes   improve wake-up latency when a thread receives
-                               a signal [no]
-    --lowlat-syscalls=no|yes  improve wake-up latency when a thread's
-                               syscall completes [no]
+    --run-libc-freeres=no|yes free up glibc memory at exit? [yes]
+    --weird-hacks=hack1,hack2,...  recognised hacks: lax-ioctls [none]
+    --signal-polltime=<time>  signal poll period (mS) for older kernels [50]
+    --lowlat-signals=no|yes   improve thread signal wake-up latency [no]
+    --lowlat-syscalls=no|yes  improve thread syscall wake-up latency [no]
     --pointercheck=no|yes     enforce client address space limits [yes]
 

--- valgrind/none/tests/cmdline2.stdout.exp  #1.4:1.5
@@ -2,5 +2,5 @@
 
   common user options for all Valgrind tools, with defaults in [ ]:
-    --tool=<name>             Use the Valgrind tool named <name>
+    --tool=<name>             use the Valgrind tool named <name>
     -h --help                 show this message
     --help-debug              show this message, plus debugging options
@@ -9,17 +9,12 @@
     -v --verbose              be more verbose, incl counts of errors
     --trace-children=no|yes   Valgrind-ise child processes? [no]
-    --track-fds=no|yes        Track open file descriptors? [no]
+    --track-fds=no|yes        track open file descriptors? [no]
 
   uncommon user options for all Valgrind tools:
-    --run-libc-freeres=no|yes Free up glibc memory at exit? [yes]
-    --weird-hacks=hack1,hack2,...  [none]
-         recognised hacks are: lax-ioctls
-    --signal-polltime=<time>  time, in mS, we should poll for signals.
-                              Only applies for older kernels which need
-                              signal routing [50]
-    --lowlat-signals=no|yes   improve wake-up latency when a thread receives
-                               a signal [no]
-    --lowlat-syscalls=no|yes  improve wake-up latency when a thread's
-                               syscall completes [no]
+    --run-libc-freeres=no|yes free up glibc memory at exit? [yes]
+    --weird-hacks=hack1,hack2,...  recognised hacks: lax-ioctls [none]
+    --signal-polltime=<time>  signal poll period (mS) for older kernels [50]
+    --lowlat-signals=no|yes   improve thread signal wake-up latency [no]
+    --lowlat-syscalls=no|yes  improve thread syscall wake-up latency [no]
     --pointercheck=no|yes     enforce client address space limits [yes]