are not entered into bugzilla tend to get forgotten about or ignored.
170510 Don't warn about ioctl of size 0 without direction hint
+241072 List tools in --help output
327548 false positive while destroying mutex
351857 confusing error message about valid command line option
392331 Spurious lock not held error from inside pthread_cond_timedwait
"\n"
" tool-selection option, with default in [ ]:\n"
" --tool=<name> use the Valgrind tool named <name> [memcheck]\n"
+" available tools are:\n"
+" memcheck cachegrind callgrind helgrind drd\n"
+" massif dhat lackey none exp-bbv\n"
"\n"
" basic user options for all Valgrind tools, with defaults in [ ]:\n"
" -h --help show this message\n"
tool-selection option, with default in [ ]:
--tool=<name> use the Valgrind tool named <name> [memcheck]
+ available tools are:
+ memcheck cachegrind callgrind helgrind drd
+ massif dhat lackey none exp-bbv
basic user options for all Valgrind tools, with defaults in [ ]:
-h --help show this message
--log-fd=<number> log messages to file descriptor [2=stderr]
--log-file=<file> log messages to <file>
--log-socket=ipaddr:port log messages to socket ipaddr:port
- --enable-debuginfod=no|yes query debuginfod servers for missing
- debuginfo [yes]
user options for Valgrind tools that report errors:
--xml=yes emit error output in XML (some tools only)
tool-selection option, with default in [ ]:
--tool=<name> use the Valgrind tool named <name> [memcheck]
+ available tools are:
+ memcheck cachegrind callgrind helgrind drd
+ massif dhat lackey none exp-bbv
basic user options for all Valgrind tools, with defaults in [ ]:
-h --help show this message
--log-fd=<number> log messages to file descriptor [2=stderr]
--log-file=<file> log messages to <file>
--log-socket=ipaddr:port log messages to socket ipaddr:port
- --enable-debuginfod=no|yes query debuginfod servers for missing
- debuginfo [yes]
user options for Valgrind tools that report errors:
--xml=yes emit error output in XML (some tools only)