| To: | Dave Brolley <brolley@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Possible QA issue in _valgrind_clean_assert |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Thu, 12 Feb 2015 19:11:22 -0500 |
| Cc: | Nathan Scott <nathans@xxxxxxxxxx>, PCP <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20150212233536.GC16895@xxxxxxxxxx> |
| References: | <170098171.4053973.1423717266752.JavaMail.zimbra@xxxxxxxxxx> <54DD2668.6020005@xxxxxxxxxx> <20150212233536.GC16895@xxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi -
> [...] I'll poke at the test case tomorrow to see if the sudo can be
> removed or valgrind placated.
This seems to work on my machines; would folks please confirm on theirs?
diff --git a/qa/common.check b/qa/common.check
index f712203b4e87..2c2bf0c9dc76 100644
--- a/qa/common.check
+++ b/qa/common.check
@@ -835,7 +835,7 @@ if which valgrind >/dev/null 2>&1; then
else
__extra=''
fi
- _valgrind_clean_assert="valgrind -q --leak-check=full --read-var-info=yes
\
+ _valgrind_clean_assert="valgrind -q --vgdb=no --leak-check=full
--read-var-info=yes \
--suppressions=$here/valgrind-suppress $__extra \
--log-fd=1"
fi
- FChE
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Possible QA issue in _valgrind_clean_assert, Frank Ch. Eigler |
|---|---|
| Next by Date: | Re: pcp updates: coverity, qa, martins+fche merges, Frank Ch. Eigler |
| Previous by Thread: | Re: Possible QA issue in _valgrind_clean_assert, Frank Ch. Eigler |
| Next by Thread: | RE: [pcp] Possible QA issue in _valgrind_clean_assert, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |