Well, unfortunately this would mean re-writing all my code using new memory
operations. Also, my error may be completely unrelated to memory
whatsoever. It would be much nicer from my standpoint to be able to call a
function to get the amount of free memory (or even check it through the
debugger).
Someone must have written some program to detect the amount of free memory.
Would anyone be willing to volunteer a solution to the problem of
determining the amount of free memory? Or at least point me in the right
direction? I'm not sure I completely understand the Palm memory model.
Thanks!
David Korus
-----Original Message-----
From: Roger Chaplin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 14, 1999 7:04 PM
To: [EMAIL PROTECTED]
Subject: Re: how to monitor memory?
Here's an idea. Since the memory allocation routines do return a null
pointer if the allocation fails, can't you just do all of your memory
allocations for a particular operation up front, and bail out if any of
them fail? This may have the disadvantage of requiring more stack space
(for local variables to hold the handles) if you're doing many separate
allocations, but it should be very reliable.
--
Roger Chaplin
<[EMAIL PROTECTED]>
