I wanted to figure out where my code was crashing on alpha-testers' devices. I ended up writing a very small utility to patch SysReset() and display the value of feature 'diaG' #1 on a blue screen. I then added a lot of FtrSet( 'diaG', 1, n ) calls in my app, and then when users reported the value displayed on the blue screen, I had some idea of where my app was last executing.
This is very simple, and there are probably better ways of doing this on one's own device, but it's a nice trick to have up your sleeve if you're having things crash on testers' devices and can't duplicate it locally, so I thought I'd share this trick. If you want a copy of Diagnoser (feel free to use it, distribute it, whatever, as long as I am not liable for anything), it's at: http://www.1src.com/freeware/index.php?cid=4 I did have a report of the need for a hard reset on a T3. I don't know if that was due to Diagnoser or due to something else. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
