Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: Tony Levatino Newsgroups: scee.yaroze.programming.3d_graphics,scee.yaroze.beginners,scea.yaroze.programming Subject: Re: greets to all Date: Sat, 09 Jan 1999 17:38:05 -0500 Organization: SCEA News Server Lines: 31 Message-ID: <3697DA4D.2DA108B9@nycap.rr.com> References: <36966D40.47664F57@vassar.edu> <01be3be9$6c109f40$0a3ddec2@guildfoc> <7782i9$m3r4@scea> NNTP-Posting-Host: toshiba-173-23.nycap.rr.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.07 [en] (Win95; U) Xref: chuka.playstation.co.uk scee.yaroze.programming.3d_graphics:1128 scee.yaroze.beginners:668 You know what the crazy thing is? Sometimes it crashes (locks up, needs a reset punch) BEFORE i malloc... :) i don't understand it. I'm not doing anything but walking a file in memory, and WELL within limits at that... :) -charles Ed Federmeyer wrote: > Miles Buzzing wrote in message <01be3be9$6c109f40$0a3ddec2@guildfoc>... > >Charles - > > > >Just on the off chance..... > > > >If you're using malloc() to create working space dynamically add some debug > >code to return the allocated address. By default malloc() allocates space > >anywhere after 0x80000000 you may find you're overwriting the NY debugger > >workspace located just below 0x80009000. > > > >- Miles > > 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