One new Coverity defect was discovered from existing code in this mornings
run. Also recent changes seem to have adjusted tests and provoked valgrind
to find/display potential leaks. That path had already been vetted previously
in a shorter stack trace - just adjust the trace to allow inclusion of more
traces.
John Ferlan (2):
tests: Coverity found new NULL_RETURNS
valgrind: Adjust filter for _dl_allocate_tls
tests/.valgrind.supp | 6 ++++--
tests/jsontest.c | 8 +++++++-
2 files changed, 11 insertions(+), 3 deletions(-)
--
1.8.1.4