|
From: David B. <dav...@gm...> - 2013-01-06 21:24:10
|
John, That's true for memcheck if interested in memory corruption issues. What about massif? It seems that if we only want memory measurements, wouldn't it be enough to just handle malloc/free/etc.? What if I want to run memcheck just to find memory leaks? Doesn't seem to me that I need actual instrumentation here of all code, no? Even for the complete memcheck functionality, some use cases may live well enough with just instrumenting a part of the program. Say I have a huge program, which contain tons of DLLs, most of them not under my responsibility and/or I can't fix the bugs in them. If I just want to memcheck my DLL, and am willing to live with the assumption that memory my DLL allocates is only read/written by my DLL, it seems reasonable to only translate and handle my DLL, no? On Sun, Jan 6, 2013 at 11:06 PM, John Reiser <jr...@bi...> wrote: > > What I want is basically to instrument only a couple of .so modules, > > leaving anything else unchanged. > > In order to compute correct answers, memcheck must observe > every instruction whose input(s) derive from memory, > or whose output(s) eventually go to memory. > "Partial instrumentation" would be possible only for > a program which directly spews constants. > > -- > > |