Displaying 2 results from an estimated 2 matches for "python_2".
Did you mean:
python2
2018 Dec 02
0
[PATCH nbdkit 3/4] valgrind: Enable valgrinding of Python plugin.
...T LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+# OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+# SUCH DAMAGE.
+
+# Python leaks lots of memory by design.
+{
+ python_1
+ Memcheck:Leak
+ fun:malloc
+ ...
+ fun:Py_InitializeEx
+}
+
+{
+ 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
+ Me...
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