I'd encountered a similiar problem, when I overruned the buffer. Look out for common C errors, e.g. using sizeof operator with structures which are aligned with compiler specific manner (and mentioned buffer overrun).
My way of tracing buffer overrun with simulator 5.4: - just hitting "home" during debug session => if you don't make proper memory clean up or overrun the buffer simulator will report error or crash. As soon as simulator display dialog, press "Debug", and than debugger will show suspicious code. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
