Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: "Ed Federmeyer" Newsgroups: scee.yaroze.programming.3d_graphics,scee.yaroze.beginners,scea.yaroze.programming Subject: Re: greets to all Date: Sat, 9 Jan 1999 17:57:15 -0600 Organization: Ed Federmeyer Lines: 27 Message-ID: <778pqg$m3r6@scea> References: <36966D40.47664F57@vassar.edu> <01be3be9$6c109f40$0a3ddec2@guildfoc> <7782i9$m3r4@scea> <3697ADE4.3F396011@vassar.edu> NNTP-Posting-Host: charlie.cns.iit.edu X-Newsreader: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Xref: chuka.playstation.co.uk scee.yaroze.programming.3d_graphics:1129 scee.yaroze.beginners:669 Charles Nicholson wrote in message <3697ADE4.3F396011@vassar.edu>... >> Yes, definitely. I had all kinds of flaky problems with malloc() until I >> realized I >> actually needed to call InitHeap() first. By flaky, I mean, sometimes the >> program would crash, sometimes not. Even if I alloc'd the exact same >> size memory each time I ran! >> >> Good luck, >> EdF > >Thanks- What should i put for my initheap params? >-charles The start address of a chunk of memory, and it's length. The docs say the length is "/4" in other words, the length in 32bit words rather than 8 bit bytes. I dunno about that. I've been using the length as in 8-bit byte quantitites and it's worked great for me. Just like any other memory-file, you need to make sure this heap area does not overlap anything else. All malloc() memory will come from within this area, so it must be big enough for all your potential malloc()s. EdF