On Tuesday, April 03, 2012, Peter Toft wrote: > Hi Valgrinders > > I am debugging a beast of C/C++ - ~800.000 lines of code.
800k LOC is small (very) compared to some .. > I see with GCC 4.5.2 and valgrind 3.7.0 on Red Hat 5.7 64 bit, that > valgrind exits with no warning. Bummer! Is it using a custom allocator, or a non-glibc malloc/free implementation (tcmalloc, jemalloc) ? That might explain it. > I do not have any $LD_PRELOAD set. Should I? Not AFAIK. J ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
