From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pltcl valgrind output |
Date: | 2017-12-20 14:47:14 |
Message-ID: | 6ab18916-272a-e513-0405-9e92e90df3e4@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/18/2017 10:12 AM, Andrew Dunstan wrote:
> I've been adding support for valgrind to the buildfarm client (code will
> hit the git repo shortly). Mostly the results have been pretty clean,
> but the pltcl tests generated the attached output. Perhaps someone with
> more valgrind-fu than I have so far would like to use the information to
> extend our supp file appropriately (or fix what it's complaining about).
The following appears to keep valgrind quiet. AFAICT the problem isn't
in our code.
diff --git a/src/tools/valgrind.supp b/src/tools/valgrind.supp
index af03051..24c6f5b 100644
--- a/src/tools/valgrind.supp
+++ b/src/tools/valgrind.supp
@@ -212,3 +212,11 @@
Memcheck:Cond
fun:PyObject_Realloc
}
+
+#### issue with TclNRRunCallbacks
+{
+ tcl_callback
+ Memcheck:Cond
+ ...
+ fun:TclNRRunCallbacks
+}
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-12-20 15:08:26 | Re: [HACKERS] Transaction control in procedures |
Previous Message | Simone Gotti | 2017-12-20 14:30:40 | Re: GSoC 2018 |