"Renaud Amar" <[EMAIL PROTECTED]> wrote in message news:69246@palm-dev-forum... > > > That's definitely a good advice ... > and actually I already have a normal application version > of my hack running on Palm OS. So I know for sure that there are no issues > with the code itself. > The problems I have are with the different issues specific to hacks... > (ok ok I admit, I'm doing nasty stuff in my hack that ...uh some palm > developers > wouldn't like to hear I guess :) )
If you're going to debug a hack, you're probably going to have to work at the assembly level. CW Palm 8 supports attaching to a stopped device (DbgBreak, hint, hint), but its not going to be able to associate the hack code resource with the debug symbolics file (the psym file) too easily. You could use Palm Debugger, the stand-alone debugger Palm supplies. It works well at the assembly level, and with proper tracing (HostTraceFoo is your friend), you have a good chance of finding your bugs. The article I wrote today on multiple segment shared libraries (see www.palmoswerks.com) could be useful too. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
