I had two instances where absolutely impossible things were happening --
once with MemSet and once with MemMove. All the args to the functions were
perfect, but I'd get bizarre results. Example: Call MemSet with address X,
and the value of the word at address X-8 would get incremented by 1. I even
wrote my own MemSet to make a problem go away temporarily (which it did)
until I could figure it out.
In both cases, I was walking off the end of a dynamic memory chunk
somewhere far removed in both time and codespace from the MemMumble
problem. As soon as I fixed the memory corruption elsewhere, the MemMumble
function worked great, the sun came out, all my stocks went up, and my golf
handicap dropped by 2 index points. Just something to keep in mind if you
see things in the debugger that cannot possibly be happening -- it may be
memory corruption and not a debugger bug.
Curtis Jackson
Director of Engineering
Aniwhere, Inc.
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
