Hi,
On 4/29/14 12:43 PM, Thomas Fankhauser wrote:
Hey there,
we are using UV in a C++ project tested with GoogleTest and want to use
valgrind.
If we run each test individually - via the gtest_filter using valgrind,
all tests run just fine and leak no memory.
But if we want to run the whole suite we get various valgrind complains,
although the tests finish successfully.
Without using MAKE_VALGRIND_HAPPY() at the end of the test, the
complains look like this:
You need to leave MAKE_VALGRIND_HAPPY, so that the loop is closed and
all resources are freed after each run.
[snip]
The issues occur on both OSX 10.9 and Arch64 with both the gcc version
4.8.2 and clang version 3.4 build chain.
We are using UV 2014.01.30, Version 0.11.19 and GoogleTest 1.7.0.
There are some comments in the test headers regarding valgrind - if we
got that right valgrind is used as usual with the command line
options --leak-check=full --quiet.
We also tried debugging the invalid read, but couldn't find out more.
Do you have any idea where this errors could come from? We assume its
somewhere along the test shutdown, but how can we fix that?
Thank you for your help, our heads are melting here!
I don't really know how to try to figure this out, but using latest
master would give matching line numbers so I can try to see if there is
something wrong. Also the code in uv_loop_delete changed quite a bit.
Not that it will fix this, though.
Cheers,
--
Saúl Ibarra Corretgé
http://bettercallsaghul.com
--
You received this message because you are subscribed to the Google Groups
"libuv" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/libuv.
For more options, visit https://groups.google.com/d/optout.
