My app has suddently started giving "bus error" messages in Pose when I'm killing a CodeWarrior debug session. When I run the app (without using the debug option) then it runs fine and does not give an error. But as soon as I try to debug I get this error only at the point where I kill the debug session. I can trace the source code right up to the point where the last instruction in my AppStop() routine have been executed. So it really looks like the error occurs when the debugger is busy terminating.
How do one find such an error? I have spent my entire Sunday afternoon and can still not figure out what to do. I do not even know what normally cause a bus error and why does it only happen at the end of a debug a session? Any tips of what to look out for would be greatly appreciated. Here is an example what the last few lines that I see the log file of POSE: 20.718: --- System Call 0xA39E: |-|-|-|-|-WinRGBToIndex. 20.718: --- System Call 0xA3E0: |-|-|-|-|-|BmpGetColortable. 20.718: --- System Call 0xA375: |-|-|-|-|-|BltFindIndexes. 20.718: --- System Call 0xA39E: |-|-|-|-|-WinRGBToIndex. 20.718: --- System Call 0xA3E0: |-|-|-|-|-|BmpGetColortable. 20.718: --- System Call 0xA375: |-|-|-|-|-|BltFindIndexes. 20.718: --- System Call 0xA035: |-|-|-|-|-MemPtrUnlock. 20.718: --- System Call 0xA061: |-|-|-|-|-DmReleaseResource. 20.797: === ERROR: **************************************************************************** **** 20.797: === ERROR: MyApp (1.0) just read from memory location 0x8003D261, causing a bus error. A "bus error" means that the application accessed a memory location that is not in RAM or ROM, nor corresponds to a memory-mapped hardware register. 20.797: === ERROR: **************************************************************************** **** Best regards Werner Terreblanche -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
