1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2026-01-27 23:50:30 -08:00
emacs/mps/qa/function/505.txt
Richard Tucker b1ab07446f New unit
new test

Copied from Perforce
 Change: 19565
 ServerID: perforce.ravenbrook.com
1998-06-02 12:50:32 +01:00

27 lines
929 B
Text

$HopeName: MMQA_test_function!505.c(trunk.1) $
TEST_HEADER
summary = SW memory leak detection
language = english
END_HEADER
1. Check out a version of SW known to be stable and reliable. It's
best to opt for one which corresponds to an actual external release,
e.g. SW_B11, which is 4.5r1.
2. Build a release version using the new memory manager. Bear in mind
that in this context, "memory manager" means not just the mmsw library,
but the glue code. If the distance between the current SW trunk and the
branch you chose is great enough, you may need to edit the new glue code
to make it compatible with the old SW.
3. Set up device and page settings. Turn on the memory statistics
page feature. Then quit and remove LOGFILE from the SW folder.
4. Start SW, run tests, quit.
5. Look at
If time permits, try on a range of platforms with a range of ScriptWorks
settings. See other SW tests for suggestions.
rit 1998-03-13