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/NEWS b/NEWS
index a5d0ae6..70a58c3 100644
--- a/NEWS
+++ b/NEWS
@@ -5,6 +5,11 @@
* ==================== TOOL CHANGES ====================
+* Memcheck:
+
+ - The leak_check GDB server monitor command now can
+ control the maximum nr of loss records to output.
+
* ==================== OTHER CHANGES ====================
* The C++ demangler has been updated so as to work well with C++