Hi,
I have a a couple of question which I hope someone can help with. I've been having a lot of fun debugging a problem on a Treo 180 and Treo 270.
Firstly, where do I get an emulator for the Treo 180/270? As there is no 180/270 download, I've downloaded the file for the Treo 300 from PluggedIn, assuming that it would have past device support as well. However... once I got it to work by replacing the Palm version (I was getting some really odd behaviour attempting to run it in a different location) I found that it only listed the Palm 90, and not even the 300. Using the 300 ROMs give you a repeated error on startup about 'AMX' writing to a location, but the 90 ROMs work.
Is the correct file available for download? I note that the advertised filename (POSE_3[1].3H1.zip) is the same for both the Treo 90 and 300 emulator, so might the download area be wrong?
Secondly, on to the actual problem. I'm developing an application using CodeWarrior 9.3 with POL. It works fine on a Treo 600, various Palm devices, and the simulators and emulators (apart from a problem on exit under the debugger on the Treo 90 emulator). Of course, I realise this means nothing, and a subtle bug could be lurking there somewhere!
However, on a real Treo 180 and Treo 270 device, the application hangs the system completely in a particular form on a key press and on application exit -- a soft reset is required and the debugger can't do anything. Interestingly enough, on the 180 the screen is corrupted with a repeating but random looking pattern. The 270 remains as it was.
The easiest point to replicate this is the key press. It's a form using CModalForm, and the hang happens in CModalForm::EventLoop(). If I put a breakpoint on the line which calls EvtGetEvent() and the next line, then press the key on the device, the device hangs rather than hits the breakpoint, so I can only assume that it is hanging within EvtGetEvent(). Which seems rather odd.
I cannot work out how to enter Shortcut ..1 to break the application. Am I looking for the right thing? I was hoping for a way of finding out exactly where the code is at the point of the hang.
Any pointers on where to go next would be very much appreciated. As I see it...
* I can't investigate the problem with the debugger, because I can't set a breakpoint just before the problem happens.
* I can't interrupt the processor to see where it is when it hangs.
* I can't find an emulator for these devices.
Thanks for any help!
Ben
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
