At 01:08 2002-12-17 -0800, you wrote:
Both. Sometimes, the extra step is harmless, but it can really confuse the debugger. Usually it can recover, but if it steps into the wrong instruction, like a trap or a jsr, you can be left with code running on the device, but the debugger not able to communicate to it anymore. You have to manually set a BP to get it to stop.Ben - So what will happen with CW V8 debugger? Does it sometimes just stop a little further on in the code than expected, or does it get totally confused?
We're not doing anything special; the debugger connection has always had the ability to modify protected data; the nub on the device does writes to memory with the protection semaphore turned off. However, this really can't be used from code running on the device, just from debuggers that are connected to the device.Your mention of overlaying code with the TRAP #0 leads me to a related question. How do you gain access to code segment? I had to remove the HwrEnableDataWrites that I used with earlier OS to allow code segment writes. There is obviously some other way to achieve this in OS/5.
--
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/
