Displaying 2 results from an estimated 2 matches for "python_4".
Did you mean:
python24
2018 Dec 02
0
[PATCH nbdkit 3/4] valgrind: Enable valgrinding of Python plugin.
...+{
+ python_2
+ Memcheck:Leak
+ fun:calloc
+ ...
+ fun:Py_InitializeEx
+}
+
+{
+ python_3
+ Memcheck:Leak
+ fun:realloc
+ ...
+ fun:Py_InitializeEx
+}
+
+# As far as I can tell there is no way to stop the Python object
+# (representing the compiled code?) from leaking from this API.
+{
+ python_4
+ Memcheck:Leak
+ fun:malloc
+ ...
+ fun:PyRun_SimpleFileExFlags
+}
+
+# This seems like a bug in Python itself.
+{
+ python_5
+ Memcheck:Leak
+ fun:malloc
+ ...
+ fun:Py_Finalize
+}
diff --git a/wrapper.c b/wrapper.c
index 3fd499b..f19c09a 100644
--- a/wrapper.c
+++ b/wrapper.c
@@ -135,7...
2018 Dec 02
10
[PATCH nbdkit 0/4] Multiple valgrind improvements and possible security fix.
I worked out why valgrind wasn't being applied to nbdkit when run by
many of the tests (patches 1-2). Unfortunately I'm not able to make
it actually fail tests when valgrind fails. Although the situation is
marginally improved in that you can now manually examine the *.log
files and find valgrind failures that way. Also adds valgrinding of
the Python plugin (patch 3).
Along the way I