|
From: Abhinav B. <abh...@gm...> - 2011-08-04 17:37:02
|
Hi, We have a query as our application uses Smartheap as memory manager on Linux x86_64 platform. So when we have issue like memory leaks, memory corruption etc we tried valgrind for the same but it was not able to detect any issues. So we decided to compile the application with OS level memory manager and valgrind starts idenitfying the errors and memory leaks. After doing more analysis we observe that valgrind uses overloaded new and delete operators for book keepings. So we were thinking that if this the case then if we compile the valgrind with Smartheap instead of OS level libraries then might we will be use the application in native formarts and not to change the memory manager for the same. So the query we have are given below 1. Can we tell valgrind to use different memory manager like passing options at compile time. If so we can use the source code of valgrind to build with Smartheap as memory manager. 2. Do we need to do some modification in the soure code or the configuration files. Thanks in advance. Regards, Abhinav |