Mercurial > emacs
changeset 32933:934a00cadb3b
Don't define SYSTEM_MALLOC so that we can find out
when it's necessary.
| author | Dave Love <fx@gnu.org> |
|---|---|
| date | Thu, 26 Oct 2000 22:08:28 +0000 |
| parents | dcf315209a36 |
| children | fa11b28f7ce5 |
| files | src/s/sol2-5.h |
| diffstat | 1 files changed, 7 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/src/s/sol2-5.h Thu Oct 26 21:51:22 2000 +0000 +++ b/src/s/sol2-5.h Thu Oct 26 22:08:28 2000 +0000 @@ -19,7 +19,13 @@ /* This is the only known way to avoid some crashes that seem to relate to screwed up malloc data after deleting a frame. */ -#define SYSTEM_MALLOC +/* rms: I think the problems using ralloc had to do with system + libraries that called the system malloc even if we linked in the + GNU malloc. I could not see any way to fix the problem except to + have just one malloc and that had to be the system one. */ +/* This is not always necessary. Turned off at present for testers to + identify any problems with gmalloc more accurately. */ +/* #define SYSTEM_MALLOC */ #if 0 /* A recent patch in unexelf.c should eliminate the need for this. */ /* Don't use the shared libraries for -lXt and -lXaw,