"Shawn" <[EMAIL PROTECTED]> wrote in message news:79387@palm-dev-forum... > > I searched the archives, but didn't get any sepcific > answers. > Can we debug a hack. If so, then what are the settings > to be followed in Code Warrior 7.0 in Windows M.E. and > the emulator/ the real device. > Thanks in adv.
It isn't really possible to debug a hack in its native form. CodeWarrior needs to be able to directly load all the code resources of the hack and lock them into memory in order to setup breakpoint and binary-to-source correspondance. Putting you hack into the format needed by the various hack managers disrupts CW's ability to load it independently. Two good debugging techniques: 1) Use the Palm Reporter and various HostControl.h calls to output debugging logs from the hack. This works if you can test your hack on the emulator. 2) Bind your hack code into an application and manually patches the traps on startup and pulls down the traps on exit. If CW can start the app, and all the trap code is in the app's segment, then you should be able to set breakpoints in the hack code. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
