At 8:53 PM +0100 2002/03/28, Aaron Ardiri wrote: > i was getting crashes with codewarrior built resources.. why? dunno. > but, it was crashing - and, this was the fix. the fix still applies > for cw release 8.
If memory serves... the first thing those extra instructions do is a push onto the stack. So, if your stack pointer hasn't been set up, or your stack is full, that would obviously cause it to explode. Does that sound like a possibility in your situation? Just curious. Long ago, before we added a hardware abstraction layer to the Palm OS, we devised a method of customizing the OS boot sequence by looking for additional ROM code tokens and executing token's data as 68k code. Generating the token data via CodeWarrior added extra stuff to the code resource starting with CW Pro 5 (...I think, plus or minus a version number). This was not a problem, except for the very first pre-RAM initialization token... because at that point in the boot sequence there was no stack (yet). So, the code pushed, the device crashed, and it sure wasn't fun debugging... nor was developing a code-resource-to-code-token tool work-around! :oP Regards, Jim Schram PalmSource Inc. Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
