Did you try running the debugger? When you run in there, you can click the debug button when the simulator crashes and it will show you the point where the code crashes. goodluck
Sincerely, Tony Janke Design Engineer II Rockford Corporation 600 S. Rockford Dr. Tempe, AZ 85281 480.337.1539 [EMAIL PROTECTED] "There are 10 kinds of people in this world...those who understand binary and those who don't." Information contained in or attached to this e-mail may be privileged, confidential, and protected from disclosure. If you are not the intended recipient of this e-mail, any review, dissemination or copying is prohibited. If you receive this message in error, please e-mail the sender immediately and delete the message and any attachments. Thank you. >>> [EMAIL PROTECTED] 09/01/05 8:07 PM >>> I encounter an odd crash running my own app on my T3. The problem does not show on other devices, nor POSE, only on an actual T3 and the T3 Simulator (I haven't checked all Simulator flavors). When I hit a given line that calls FrmShowObject on a previously shown gadget, the Simulator plainly crashes (I naively thought it was designed to help find bugs, not to go down with them ;) I suspect some form of memory corruption occurring prior to the crash. Are there strategies to debug such problems? Is all I need for on-device debugging with CW 9.3 is a serial cable hooked to the T3? As a side effect, I note that sometimes, after this crash, my hardware buttons get reassigned to different applications (all 4 were linked to Planetarium last time) even if everything remains unchanged in the Buttons tab of the Prefs program. This and the crash also appeared on another T3. -- Luc Le Blanc -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
