I think jemalloc is configuring itself to support valgrind. Running
configure shows me this:
./configure --with-jemalloc-prefix=je_ | grep -i valgrind
checking whether valgrind is compilable... yes
valgrind : 1
Looks like the header files you mentioned are in the right place:
/usr/local/include/valgrind/ | grep -E "(valgrind|memcheck)"
memcheck.h
valgrind.h
Is it OK for me to just ignore these error messages? If it's just a
missconfiguration of jemalloc's valgrind support, I'm fine with that.
best regards,
Daniel Mezzatto
On 12/12/2012 02:02 PM, Jason Evans wrote:
Is jemalloc configuring itself to support valgrind? In order for valgrind
configuration to succeed, it needs to be able to find the valgrind headers
(valgrind/valgrind.h and valgrind/memcheck.h). It's conceivable that
jemalloc's valgrind support might have some holes (it's pretty tricky to get
totally right), but the valgrind errors you pasted look like ones that would
occur if jemalloc were completely missing valgrind support.
Thanks,
Jason
_______________________________________________
jemalloc-discuss mailing list
[email protected]
http://www.canonware.com/mailman/listinfo/jemalloc-discuss
