source: git/kernel/HOWTO.FindMemoryHoles @ 75f460

Last change on this file since 75f460 was 75f460, checked in by Hans Schoenemann <hannes@…>, 9 years ago
  • Property mode set to 100644
File size: 938 bytes
1Here is a first short HowTo on how to locate memory holes in Singular:
21.) Make sure you build with -DOM_TRACK=5 (e.g. use Singulart, Singularg).
32.) Use system("mtrack", [<level>, [<filename>]]) to get a report about
4    unused memory, where
5 * 0 <= level <= 5 determines how many stackframes per not freed
6   address are printed (default is 5 -- 0 only prints a summary)
7 * <filename> is name of file where report should be output to
8   (defaults to stdout).
93.) Running 'regress.cmd -tt <level> file.tst' creates the file
10    'file.mtrack.unused' with report of not freed addresses (<level> has
11    same meaning as above).
124.) Within the C/C++ sources, Use 'omMarkAsStatic(addr)' to mark an
13    address as static, i.e. as an address which is ok if it is not
14    freed. Addresses marked this way are not reported by
15    system("mtrack",...) (resp. regress.cmd -tt).
165.) For some more details, see also system("mtrack", ...)
Note: See TracBrowser for help on using the repository browser.