More often than not when you try to re-start a debugging session - the debugger cant connect to it - and you end up having to tear the simulator down and start again. (and you more often than not have to check that there isnt a zombied PalmSim process still running away with your CPU somewhere). I have found deleting the app from the simulator before trying to re-run the debugger can prevent this hang up sometimes.
Are you using CW V9's ability to start and kill PalmSim for you? We added that to help work around problems. Since the debugger actually kills the process, it should avoid zombies hanging around.
I'd not seen the "can't set breakpoints" issue, but I think I know what's happening. If you look in bin\plugins\support\Palm_OS\PalmEmulators.xml, you'll see that we use a switch to turn off write-protection in the storage heap when CW starts PalmSim -- I think this was needed because we weren't able to modify the program code in memory over the debug interface in some situations, and we need to be able to modify code to set breakpoints.
I recently fixed a bug where CW wasn't letting you see some memory allocated by the OS using PalmSim -- I'm not sure if that fix was in 9.2... basically, PalmSim didn't tell the debugger the proper ranges for valid memory spaces, and some things, like the EventType structure that got passed to the user program, were seen outside this range.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
