Chris Tutty wrote:
Be careful here. Crashes which go away when you change theThanks, Chris. Some good points. I will have to remember that.
code are often memory corruption. This sort of bug is often an uninitialised or corrupt pointer that is writing over memory at an offset. The crash occurs because the over-write destroys important data or writes over program code. When you add debugging lines you change the size of your compiled code which can shift the offset of the over-write to a section of memory that isn't important (or which you aren't testing).
Since I am still feeling my way along, and since this is an open-source program, it may end up being someone other than me who finds this and fixes it.
--Larry
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
