Xref: utzoo comp.lang.c:30416 comp.sys.ibm.pc.misc:138 comp.bugs.misc:295
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!mintaka!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!kubix!mad-2
From: mad-2@kub.nl (C. Wekx)
Newsgroups: comp.lang.c,comp.sys.ibm.pc.misc,comp.bugs.misc
Subject: Turbo C 2.0 MaLfUnCtIoNiNg?
Keywords: Turbo C 2.0   bug   malloc
Message-ID: <1217@kubix.kub.nl>
Date: 20 Jul 90 10:53:57 GMT
Followup-To: comp.lang.c
Organization: KUB Univ., Tilburg, The Netherlands.
Lines: 12


Yo folks,


	does anyone happen to know why Turbo C 2.0's malloc
function is malfunctioning? They do not always signal an out of memory
situation, but overwrite the first part of their segment instead.




						Joris