|
From: Nicholas N. <nj...@cs...> - 2007-04-04 22:08:37
|
On Wed, 4 Apr 2007, Ashley Pittman wrote: > I'd need a tool which dumped allocations (along with calling stack), > deallocations and memory accesses, this could then be piped to a > external process which would report: > > 1) Memory that is never written to or read from. > 2) Memory that is written to but never read from. > 3) Memory that is only used soon after creation and never again. > 4) Invalid reads. > 5) Reads from uninitialised memory. I wrote a tool ages ago that tried to do 1, 2, and 3. IIRC I got bazillions of warnings out of it from code out of my control, and I quickly gave up. But I didn't spend very long on it, and my understanding of all this stuff was much less back then, so don't let me discourage you from trying it :) Nick |