Hi Xavier,
On Sun, Mar 20, 2016 at 1:50 PM, Xavier Besseron
wrote:
> Hi Aaron,
>
> I don't know if that's what you're looking for,
> but you can try to set Valgrind options using an environment variable or
> a cmake variable
>
> set(VALGRIND_OPTS "--suppressions=/path/to/your_suppression_file.s
On Tuesday 08 March 2016, 10:00:00 wrote Nicholas Braden:
> Jakob, I don't think there is any confusion about what REQUIRED means.
> Whether or not REQUIRED is provided, the list of OPTIONAL_COMPONENTS
> should not be required under any circumstances. The example error
> message seems pretty clear
Hi Aaron,
I don't know if that's what you're looking for,
but you can try to set Valgrind options using an environment variable or a
cmake variable
set(VALGRIND_OPTS "--suppressions=/path/to/your_suppression_file.supp")
or
export VALGRIND_OPTS="--suppressions=/path/to/your_suppression_file.su
My program links to libstdc++. It turns out there is a well-known false
positive
from valgrind regarding libstdc++ memory pools.
http://valgrind.org/docs/manual/faq.html#faq.reports
How may I suppress this error when running ctest -D NightlyMemCheck ?
Thanks,
Aaron
--
Powered by www.kitware.c
On Sun, Mar 20, 2016 at 8:46 AM, Aaron Boxer wrote:
> I recently added pthreads to my cmake program.
> When I run valgrind, I get a "blocks still reachable" warning,
> coming from dl_init.
>
> I suspect that pthreads is not cleaning up properly. Is there a way
> of ensuring that the shared librar
I recently added pthreads to my cmake program.
When I run valgrind, I get a "blocks still reachable" warning,
coming from dl_init.
I suspect that pthreads is not cleaning up properly. Is there a way
of ensuring that the shared library for pthreads gets cleaned up correctly
via cmake?
i.e. a match
