Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!sdsu!ucselx.sdsu.edu!petunia!polyslo!jdudeck
From: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Is there a bug in MSC 5.1 malloc for far data?
Message-ID: <25f8a7cd.ca@polyslo.CalPoly.EDU>
Date: 10 Mar 90 07:07:57 GMT
Reply-To: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 14


I have been having trouble with a compiler project that I am doing in
MS C 5.1.  It appears that malloc() is sometimes getting hung in a very
tight loop.  It doesn't happen all the time.  If I run my program
right after rebooting it always works, but if I run it right after a
compile, sometimes malloc hangs.  If I run it in CodeView and this happens
I can stop it with Ctrl-Break, and step through the machine language,
and it is stuck in the library routine in a very tight (about 6 instructions)
loop.

I am using the compact memory model, on a 386/20, and MS-DOS 4.01.

Just wondering if this is a known bug, or a common programmer error of some
sort?

-- 
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.