diff options
| author |  Thomas Rast <trast@inf.ethz.ch> | 2013-03-31 10:00:17 +0200 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2013-04-01 07:45:41 -0700 |
| commit | 95d9d5ec75d3549f00cac29cd33be899cfb4693a (patch) | |
| tree | 698c3d8d05b7f078b61dd25c6963c1d54fa6407d /t/README | |
| parent | tests: parameterize --valgrind option (diff) | |
| download | tgif-95d9d5ec75d3549f00cac29cd33be899cfb4693a.tar.xz | |
tests --valgrind: provide a mode without --track-origins
With --valgrind=memcheck-fast, the tests run under memcheck but
without the autodetected --track-origins. If you just run valgrind to
see *if* there is any memory issue with your program, the extra
information is not needed, and it comes at a roughly 30% hit in
runtime.
While it is possible to achieve the same through GIT_VALGRIND_OPTIONS,
this should be more discoverable and hopefully encourage more users to
run their tests with valgrind.
Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/README')
| -rw-r--r-- | t/README | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -106,6 +106,11 @@ appropriately before running "make". 'drd', but you may use any tool recognized by your valgrind installation. + As a special case, <tool> can be 'memcheck-fast', which uses + memcheck but disables --track-origins. Use this if you are + running tests in bulk, to see if there are _any_ memory + issues. + Note that memcheck is run with the option --leak-check=no, as the git process is short-lived and some errors are not interesting. In order to run a single command under the same |