Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!ssbell!mcmi!amperif!zycor!bill
From: bill@zycor.UUCP (bill)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Possible bug in MSC malloc (Large Memory Model)
Keywords: malloc, bug MSC5.1
Message-ID: <205@zycor.UUCP>
Date: 18 May 89 15:24:11 GMT
References: <1071@koko.CSUStan.EDU> <1447@optilink.UUCP> <1659@ozvax.WV.TEK.COM>
Reply-To: bill@zycor.UUCP (bill)
Distribution: usa
Organization: zycor, Inc. - Omaha, NE
Lines: 24

In article <1659@ozvax.WV.TEK.COM> wesw@ozvax.UUCP (Wes Whitnah) writes:
>
>   There are bugs in MSC and/or DOS (verified VERBALLY to me by
>   some MicroSoft Engineers a few years back -- see description
>   below for details...) when heavily manipulating memory using
>   the Large Memory Model -- by heavily manipulating memory I
>   mean allocating and freeing memory VERY often.   Most memory
>   bugs I have seen though are in the application itself.
>
Does this imply that a program compiled in the compact model
(small code, big data) does the same thing? Also, does the size
of the blocks make a difference? I have an application that uses
large model memory and does malloc/free all over the place of
blocks that are about 40 bytes long. Should I look harder and see
if this problem is happening, or is it only when there are large
"chunks" of memory being malloc'd? Enquiring minds want to know.

Bill Mahoney
bill@zycor.UUCP
Warning: Driver breaks for 2400 baud.
-- 
Bill Mahoney
bill@zycor.UUCP
Warning: Driver breaks for 2400 baud.