Xref: utzoo comp.sys.ibm.pc:28761 comp.lang.c:18666
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!ames!winken!csustan!koko!jb
From: jb@CSUStan.EDU (John Birchfield)
Newsgroups: comp.sys.ibm.pc,comp.lang.c
Subject: Possible bug in MSC malloc (Large Memory Model)
Keywords: malloc, bug MSC5.1
Message-ID: <1071@koko.CSUStan.EDU>
Date: 12 May 89 14:49:22 GMT
Reply-To: jb@koko.csustan.edu.UUCP (John Birchfield)
Distribution: usa
Organization: Calif. State Univ., Stanislaus, Turlock, Ca
Lines: 21

I have a program which does directory scanning in a big way and I am
finding that the program corrupts memory and behaves in a more or less
irrational manner when the Large Memory Model is used.

The errors reported relate to the inability to allocate memory and the
program failing or that DOS reports memory as being corrupted and
can't load COMMAND.COM when the program terminates.

The problems dissappear when I use the Small Memory Model - I know that this
sounds like the old pointer size problem but I have looked over the places
the program does mallocs and frees and they seem to be correct.

The question then is IS THERE A KNOWN BUG IN MALLOC USING THE LARGE MEMORY
MODEL???

thanks
-                                                                      -
===                                                                  ===
John Birchfield                                       1575 Quail Ct.
jb@koko.csustan.edu                                   Turlock, CA  95380
                                                      (209) 634-6243