From 1765c0f9baf16ff1c2f5f109fb31e411831f0945 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Mon, 18 Jun 2012 22:30:27 +0930 Subject: ntdb: catch any valgrind errors in test Make --valgrind and --valgrind-log options work! Amitay figured this out! Signed-off-by: Rusty Russell --- lib/ntdb/wscript | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/ntdb/wscript b/lib/ntdb/wscript index aab42456c5..fd9c96b59b 100644 --- a/lib/ntdb/wscript +++ b/lib/ntdb/wscript @@ -230,9 +230,9 @@ def testonly(ctx): if not os.path.exists(link): os.symlink(os.path.abspath(os.path.join(env.cwd, 'test')), link) - if Options.options.VALGRIND: + if env.options['VALGRIND']: os.environ['VALGRIND'] = 'valgrind -q --num-callers=30 --error-exitcode=11' - if Options.options.VALGRINDLOG is not None: + if env.options['VALGRINDLOG']: os.environ['VALGRIND'] += ' --log-file=%s' % Options.options.VALGRINDLOG for f in env.NTDB_TEST_RUN_SRC + env.NTDB_TEST_API_SRC: -- cgit