Philippe Waroquiers 48046f6940 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

2012-01-14 13:53:13 +00:00

..

mc-manual.xml

Added a new parameter to the memcheck 'leak_check' GDB monitor command

2012-01-14 13:53:13 +00:00

mc-tech-docs.xml

We currently use a mix of <option> and <computeroutput> tags for command

2009-07-30 02:57:52 +00:00