On Thu, Apr 30, 2009 at 10:28 AM, Bart Van Assche <[email protected]> wrote: > On Wed, Apr 29, 2009 at 7:56 PM, <[email protected]> wrote: >> This is my first post. I am using Valgrind 3.4.1. The application I was >> testing for what seems to be memory corruption is compiled along with >> dlmalloc-2.8.3.c > > Have you considered to relink your application such that it uses > glibc's memory allocator instead of dlmalloc before analyzing it with > Helgrind or DRD ?
That may or may not work depending on a particular use of a custom malloc library. In our case (we use tcmalloc) we cannot replace the custom malloc with the glibc's malloc because many our applications rely on the fact that we use tcmalloc. --kcc > > Bart. > ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
