Added a new parameter to the memcheck 'leak_check' GDB monitor command
to let the user specify a max nr of loss records to output : on huge
applications, interactive display of a lot of records in gdb can
take a lot of time.
* mc_include.h :
- added UInt max_loss_records_output; to LeakCheckParams structure
- avoid passing LeakCheckParams by struct copy.
* modified test gdbserver_tests/mcleak to test the new parameter
* mc_main.c : parse or set max_loss_records_output in leak_check cmd
handling and calls.
* mc-manual.xml : document new leak_check parameter
* mc_leakcheck.c :
- extract printing rules logic in its own function
- in print_results, if there is a limit in LeakCheckParam,
compute from where the printing of loss records has to start
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12329 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/gdbserver_tests/mchelp.stdoutB.exp b/gdbserver_tests/mchelp.stdoutB.exp
index de9f74f..a12b4c4 100644
--- a/gdbserver_tests/mchelp.stdoutB.exp
+++ b/gdbserver_tests/mchelp.stdoutB.exp
@@ -23,9 +23,11 @@
and outputs a description of <addr>
leak_check [full*|summary] [reachable|possibleleak*|definiteleak]
[increased*|changed|any]
+ [unlimited*|limited <max_loss_records_output>]
* = defaults
Examples: leak_check
leak_check summary any
+ leak_check full reachable any limited 100
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
@@ -60,8 +62,10 @@
and outputs a description of <addr>
leak_check [full*|summary] [reachable|possibleleak*|definiteleak]
[increased*|changed|any]
+ [unlimited*|limited <max_loss_records_output>]
* = defaults
Examples: leak_check
leak_check summary any
+ leak_check full reachable any limited 100
monitor command request to kill this process