'DeLuxe' memory leak detector (2.0.32)

• Patch Index 2.0 Unofficial Patches
  
• Previous Patch: Virtual Terminal Driver Keyboard Security (2.0.32)
  
• Next Patch: SystemFS (2.0.xx)
  

ok, this is the next, 'DeLuxe' version of the memleak detector, against vanilla 2.0.32.

Bugfixes:

• systems with more than 64M RAM should work now (Chris Adams) actually, up to (and including) 1 Gigs of memory should be OK.

• as Peter Andres has noticed, modules have to be recompiled, and binary-only modules cannot be memleak-traced ...
  [Peter, your Peter_Andres@Auto.ITTInd.Com address doesnt work...]

• [+various cleanups]

New Features:

• 'object allocation timestamps', now the detector timestamps every memory object with a granularity of ~5 seconds.

  'very old but still allocated objects' are good leak candidates..

  timestamps are displayed in absolute time, this way allocation maps can be effectively compressed via RCS. 'current time' is displayed in the first line of /proc/memleak. (suggested by Lorenzo M. Catucci) Lorenzo's memcheck.sh script stores the current allocation map into RCS.

• reduced allocation map size via 'dynamic ID allocation'. Even with the addition of timestamps, it's smaller than the first patch, 3.6M on my system. (reduction was suggested by many people, looks like this is a problem :)

• 'findaddr.c', a smallish program which finds out wether some memory object is actually stored in memory (/proc/kcore) somewhere. If an address does not show up anywhere, it might be a leaked object ... The code is a bit ugly since it tries to prevent finding the address in it's own address space ... ;)

• lotsa smallish scripts to ease postprocessing, and a FAQ

This version has been running on my system for a few hours now, without any performance or stability problem.

Comments, reports, feature requests, flames welcome, lemme know if i've messed up somewhere.

-- mingo