Thank you for the advice. However, the trick won't help my current problem which manifests itself only when receiving a beam at a point when my app is not running. In that scenario, using the loopback trick is impossible because I need the app to be not running for the bug to appear but the app needs to be running in order to initiate the beam. Therefore, I need to be able to send the beam from a second device.
Since the bug only appears when a beam is received when the app isn't running, I am sure I am accessing a global variable somewhere. I just can't figure out where, and stepping through the code would really help.
Has anyone successfully used the debugger on a device while receiving an actual beam from a second device?
-Sean
On Wednesday, July 16, 2003, at 10:13 PM, Neil Rhodes wrote:
Use Shortcut-tap-tap-T to turn on beam loopback (anything beamed will instead be sent back to the same device without using IR). Then, you can test beam receive by sending a beam from the same device. Debugging will work because you won't be using the IR transceiver.
Neil On Wednesday, July 16, 2003, at 05:51 AM, red2 wrote:
I apologize if this is a double post. I tried to make a similar post yesterday, but have not seen it come through, so I am trying again.
I am hoping someone can help me solve a problem I am having debugging beam receiving using a Palm III attached by a serial cradle to an Windows XP box running Codewarrior 9.1
I general, I can debug fine, stepping through code that is running on the Palm III. If I set a breakpoint, code execution stops and I can step through from that point.
However, when I set a break point within my beam receive code, instead of dropping into the debugger when I receive a beam the Palm III just freezes and Codewarrior does not drop into the debugger.
If I do not set a breakpoint in my beam receive code and I receive a beam, my app receives the beam and continues to run fine. So somehow there is a problem with the breakpoint being set within the beam receive code and I can't figure out what it is. Is there a way to force Codewarrior to drop into the debugger, even if a breakpoint is not set?
If anyone can give me any advice at all I would greatly appreciate it.
Sean Kennedy Eclipta Software http://www.eclipta.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
-- Neil Rhodes Palm OS Certified Developer Co-author: Palm Programming: the Developer's Guide Available for contract programming [EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
