Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!usc!orion.oac.uci.edu!uci-ics!jarthur!petunia!polyslo!jdudeck
From: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Is there a bug in MSC 5.1 malloc for far data?
Message-ID: <25fbf969.28aa@polyslo.CalPoly.EDU>
Date: 12 Mar 90 19:32:57 GMT
References: <25f8a7cd.ca@polyslo.CalPoly.EDU> <3757@plains.UUCP>
Reply-To: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 8


Thanks to those that have responded to my query about malloc().  I asked
it because I wanted to know whether there was a "known bug", or whether
to look further in to my code.  In the end I found the problem totally
elsewhere in my program, where some pointer manipulation managed to
hose up MS-DOS (I was clobbering low addresses).  I found the problem
when I compiled it on a Unix system that gave me a core dump on the 
offending operations.

-- 
John Dudeck                           "You want to read the code closely..." 
jdudeck@Polyslo.CalPoly.Edu             -- C. Staley, in OS course, teaching 
ESL: 62013975 Tel: 805-545-9549          Tanenbaum's MINIX operating system.