git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/8] valgrind series

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 3, 2009, 23:25 UTC
Message-ID
<alpine.DEB.1.00.0902040020380.9822@pacific.mpi-cbg.de>
Yes, it has grown a little bit.
The main differences since last time:
- split out some parts that Peff thought were independent of valgrind
- added some convenience, such as "--tee" to output not only to the 
  terminal, but also to files named after the tests
- fixed half a bug in test-lib.sh (the templates were assumed to be 
  located relative to the binaries, not relative to the TEST_DIRECTORY)
- found the cause (sort of) of the spurious zlib "error".  Mark promised 
  that next zlib will contain a fix for that.
- tested.  A lot.
Note: I am not quite sure if the order is okay, but I really spent quite 
some time to reorder and resplit all the patches.
Jeff King (1):
  valgrind: ignore ldso and more libz errors
Johannes Schindelin (7):
  Add valgrind support in test scripts
  Valgrind support: check for more than just programming errors
  test-lib.sh: optionally output to test-results/$TEST.out, too
  t/Makefile: provide a 'valgrind' target
  Add a script to coalesce the valgrind outputs
  Tests: let --valgrind imply --verbose and --tee
  test-lib: avoid assuming that templates/ are in the GIT_EXEC_PATH
 t/Makefile              |    5 ++-
 t/README                |   18 +++++++-
 t/test-lib.sh           |   91 +++++++++++++++++++++++++++++++++-
 t/valgrind/.gitignore   |    2 +
 t/valgrind/analyze.sh   |  123 +++++++++++++++++++++++++++++++++++++++++++++++
 t/valgrind/default.supp |   43 ++++++++++++++++
 t/valgrind/valgrind.sh  |   13 +++++
 7 files changed, 290 insertions(+), 5 deletions(-)
 create mode 100644 t/valgrind/.gitignore
 create mode 100755 t/valgrind/analyze.sh
 create mode 100644 t/valgrind/default.supp
 create mode 100755 t/valgrind/valgrind.sh
Message 1 of 1 in “valgrind series”
  1. 0/8 valgrind seriesJohannes Schindelin, Feb 3, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.