On Jul 8, 2013, at 9:23 AM, Piyush Patel wrote: > I've ran into similar issue that Daniel Mezzato ran into(email thread around > Dec 11, 2012). > > [...] > > jemalloc: 3.4.0
jemalloc 3.3.1 included pretty major changes to valgrind integration, which I'd hoped would be the end of such spurious warnings (the previous report was in the context of 3.2.0). Your test case should make this bug pretty straightforward to track down; thanks! Jason _______________________________________________ jemalloc-discuss mailing list [email protected] http://www.canonware.com/mailman/listinfo/jemalloc-discuss
