bagpiper@csvax.caltech.EDU (06/25/87)
* pn eopy1 eopy2 eopn3 ffy hfy eon lm 010 sl 017 rm 070 sr 064 pi 005 ps 001 pl 060 hd 000 ft 000 fp 001 ts 007 012 Lately I have heard a lot of grumblings about how MS C manages memory. I assume that these problems also exist in IBM C. Could anyone who has had problems please mail me and tell me exactly what your problems were (send code samples if legal and feasible), and how you fixed them. I am currently working on a large project that malloc's large ammounts of memory in small chuncks. When we were developing the product, all of the programmers used virtual(ram) disks. One day someone tried to get the thing to run on a machine without a ram disk. Guess what happened?? It locked up the whole thing (a true blue PC) and all we could do is use the big red switch. We traced the thing down to a routine that scrunches graphic screens stores them and then, later, as needed, unscrunces them and displays them (actually it is two routines...the problem happens in the unscrunch portion). This function mallocs space. With a ram disk it flys...without, it dies mallocing memory. Any ideas????? Thanks for any and all help!! Michael Hunter (programmer) MicroCosm, Inc. day:1-213-539-9444 UUCP : ....{seismo, rutgers, ames}!cit-vax!oxy!bagpiper Box 241 ARPA : oxy!bagpiper@csvax.caltech.edu Occidental College BITNET: oxy!bagpiper@hamlet.bitnet Los Angeles, CA 90041 CSNET : oxy!bagpiper%csvax.caltech.edu@relay.cs.net