Displaying 2 results from an estimated 2 matches for "nbdkit_5".
Did you mean:
nbdkit_
2018 Dec 02
0
[PATCH nbdkit 2/4] valgrind: Add --show-leak-kinds=all and comprehensive list of suppressions.
...in various
# *_open functions are fairly inevitable. We simply have to check by
# hand that the following leaks are not possible under normal
# circumstances, and then add them to this list.
{
- nbdkit_4
+ nbdkit_3
Memcheck:Leak
fun:malloc
fun:error_open
@@ -73,7 +64,7 @@
}
{
- nbdkit_5
+ nbdkit_4
Memcheck:Leak
fun:malloc
fun:file_open
@@ -81,7 +72,7 @@
}
{
- nbdkit_6
+ nbdkit_5
Memcheck:Leak
fun:malloc
fun:memory_open
@@ -89,7 +80,7 @@
}
{
- nbdkit_7
+ nbdkit_6
Memcheck:Leak
fun:malloc
fun:null_open
@@ -97,7 +88,7 @@
}
{
- nbdkit_8
+...
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