Browse Source
This test builds a tree in a previously uninitialized buffer, then writes the whole buffer out to a file to be used by other tests. Because part of the buffer may be uninitialized this causes a valgrind error. Pre-initializing the buffer would remove the error, however it would make valgrind not notice any accesses to the uninitialized portion *before* the write out, and those would be genuine errors. So, instead we use a valgrind suppressions file - however it has a couple of problems. First it unnecessarily lists the same call path twice. Second, the call path is only right for some C library versions. Change the second copy to cover possible path that occurs with a different glibc version. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>main

1 changed files with 1 additions and 1 deletions
Loading…
Reference in new issue