Changeset daa13f in git for Singular/HOWTO.FindMemoryHoles


Ignore:
Timestamp:
Mar 10, 2014, 2:16:22 PM (10 years ago)
Author:
Hans Schoenemann <hannes@…>
Branches:
(u'spielwiese', 'a719bcf0b8dbc648b128303a49777a094b57592c')
Children:
91dd8a5ef5bb06f9f51df16f59786c2ff90de8ca
Parents:
70d976d3bfd86a066c9e62325769fb948f8735249bb56c19a835494d592e023dcce31c901eceefc5
Message:
Merge pull request #536 from mmklee/factory_noPP

Factory no pp
File:
1 edited

Legend:

Unmodified
Added
Removed
  • Singular/HOWTO.FindMemoryHoles

    r9bb56c1 rdaa13f  
    1 Here is a first short HowTo on how to locate memory holes in Singular:
    2 1.) Make sure you build with -DOM_TRACK=5 (e.g. use Singulart, Singularg).
     1Here is a HowTo for locating memory holes in Singular:
     2
     30.) disable optimization and define flag OM_TRACK=5 :
     4     set 
     5       CXXFLAGS=" -O0 -DOM_TRACK=5 "
     6         CFLAGS=" -O0 -DOM_TRACK=5 "
     7     explicitly, since configure option '--disable-optimizationflags' does not enable -O0
     8
     91.) configure Singular with options
     10     " --enable-debug --with-track-fl --with-track-backtrace "
     11     or similar (see available options from 'cd omalloc/ && ./configure --help )
    3122.) Use system("mtrack", [<level>, [<filename>]]) to get a report about
    413    unused memory, where
Note: See TracChangeset for help on using the changeset viewer.