Changeset c31461 in git
- Timestamp:
- Mar 7, 2014, 10:07:29 PM (10 years ago)
- Branches:
- (u'spielwiese', '8e0ad00ce244dfd0756200662572aef8402f13d5')
- Children:
- 70d976d3bfd86a066c9e62325769fb948f873524
- Parents:
- 4ed86341d5d2626ed91cbd40751801c58a8be5ac
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
Singular/HOWTO.FindMemoryHoles
r4ed8634 rc31461 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). 1 Here is a HowTo for locating memory holes in Singular: 2 3 0.) 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 9 1.) configure Singular with options 10 " --enable-debug --with-track-fl --with-track-backtrace " 11 or similar (see available options from 'cd omalloc/ && ./configure --help ) 3 12 2.) Use system("mtrack", [<level>, [<filename>]]) to get a report about 4 13 unused memory, where
Note: See TracChangeset
for help on using the changeset viewer.