From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: [PATCH 2/2] test-runner: set --show-leak-kinds=all
Date: Wed, 19 Jan 2022 15:04:52 -0800 [thread overview]
Message-ID: <20220119230452.2306995-2-prestwoj@gmail.com> (raw)
In-Reply-To: 20220119230452.2306995-1-prestwoj@gmail.com
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
This enables leak checks starting in main() which were previously
ignored.
---
tools/test-runner | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/test-runner b/tools/test-runner
index c35466c1..7176deaf 100755
--- a/tools/test-runner
+++ b/tools/test-runner
@@ -673,6 +673,7 @@ class Namespace:
if self.args.valgrind:
args.extend(['valgrind', '--leak-check=full', '--track-origins=yes',
+ '--show-leak-kinds=all',
'--log-file=/tmp/valgrind.log.%p'])
args.extend(['iwd', '-p', iwd_radios, '-E'])
--
2.31.1
reply other threads:[~2022-01-19 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220119230452.2306995-2-prestwoj@gmail.com \
--to=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox