Tony Janke a écrit : > 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
When I say that Simulator crashes, I don't mean that my app crashes, but that Simulator itself crashes. All I get then is a Microsoft dialog asking me whether I want to report the error to them and the program simply disappears from the desktop; the CW debugger then reports the target has unexpectedly broken the link. Simulator seems especially vulnerable, that's why I do as much testing as I can under POSE, which often allows me to find bugs that plainly crash Simulator. Alas, in this case, the bug doesn't happen under POSE, nor on my OS 3-4 devices :( -- Luc Le Blanc > >>> [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/
