I finally managed to fix the bug by simply removing the line that would
cause the crash (...) It turned out to be redundant, so no functionnality
is lost and everything else works fine beyond that. I still can't explain
what was wrong, nor why it only crashes on a T3 (I suspected color, but I
had no problem on a color CliƩ) nor why Simulator cannot debug this but
only crash. But as I have many other things I can worry about, I'll just
enjoy this magic ending.

--
Luc Le Blanc


I previously wrote:

> 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/

Reply via email to