From: "David Beers" <[EMAIL PROTECTED]> > I receive a fatal PalmSim.exe Application Error (instruction at 0x0x8881a8 > referenced memory at 0x00000000) every time my application tries to pass a > frmCloseEvent for a particular form to FrmDispatchEvent. (Other > I've been using the PalmSim a lot this week developing a PalmOS 5 app and I've found that it's not very robust with regard to application faults. Even the debug version seems to have no defensive coding in place to trap application dumbness.
What this means is that when the PalmSim crashes you have to look for the bug in your code. I've found that it's particularly flakey with regard to PalmOS functions getting NULL pointers when they shouldn't. As examples of stuff I've done wrong that's crashed it: accessing global variables from a notification launch, setting a popup list to ownerdraw (I was using the wrong list pointer so I'm not sure why the crash was happening since it was quickly fixed), mismanagement of the chunk a field control was using, etc. All traceable to bugs in my code. Although I accept that my code shouldn't have these bugs in it, the usefulness of a debugging environment that crashes when a bug occurs is fairly limited. I'm dreading the day I get a hard-to-trace fault. Anyway, I think you're going to have to start looking for form structure corruption or mismanaged memory associated with a form control. Have fun :-) Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
