Changeset 70d976 in git for Singular/HOWTO.FindMemoryHoles

Timestamp:

Mar 10, 2014, 2:15:11 PM (10 years ago)

Author:

Hans Schoenemann <hannes@…>

Branches:

(u'spielwiese', 'e7cc1ebecb61be8b9ca6c18016352af89940b21a')

Children:

daa13f7cda0d499a1e8ef40d88b9b73bf2494fc2

Parents:

283b70e49eea4578aec6c525038a9ce8df08977bc31461d231f9fdd0c0b673f01d45452a804692e0

Message:

Merge pull request #535 from surface-smoothers/update.memoryholes.HOWTO

update FindMemoryHoles howto

File:

• Singular/HOWTO.FindMemoryHoles (modified) (1 diff)

Singular/HOWTO.FindMemoryHoles

@@ -1 @@
-Here is a first short HowTo on how to locate memory holes in Singular:
-1.) Make sure you build with -DOM_TRACK=5 (e.g. use Singulart, Singularg).
+Here is a HowTo for locating memory holes in Singular:
+
+0.) disable optimization and define flag OM_TRACK=5 :
+     set  
+       CXXFLAGS=" -O0 -DOM_TRACK=5 " 
+         CFLAGS=" -O0 -DOM_TRACK=5 " 
+     explicitly, since configure option '--disable-optimizationflags' does not enable -O0
+
+1.) configure Singular with options 
+     " --enable-debug --with-track-fl --with-track-backtrace " 
+     or similar (see available options from 'cd omalloc/ && ./configure --help )
 2.) Use system("mtrack", [<level>, [<filename>]]) to get a report about
     unused memory, where