In article <81608@palm-dev-forum>, [EMAIL PROTECTED] says... > > It's written in pure "C", not C++, so no custom destructors. FWIW, it is a > multi-segment app, linked with the MSL Runtime Palm OS (2i).Lib for runtime. > The startup code is first in the segment list, and is in the same segment as > Starter.* . > > > "Keith Rollin" <[EMAIL PROTECTED]> wrote in message > news:81606@palm-dev-forum... > > > > My guess would be that some runtime cleanup code is crashing. Does > > your application have any global objects with custom destructors? > > They'd be called around the time you show the crash occurring. > > > > -- Keith Rollin > > -- Palm OS Emulator engineer > > > > > > At 10:43 PM -0600 3/26/02, Darren DeLoach wrote: > > >Here's the call stack in the debugger at the moment of the error: > (PalmOS > > >3.5 debug ROM running as a color IIIC device) > > > > > >0x10C9EAF2 (__Startup__) > > >0x10C9F10E (PilotMain) > > >0x10C9EBC8 (UIAppShellMain) > > >0x10C9EF8C (PrvAppLaunchLoop) > > >0x10C0E4B0 (PrvCallWithNewStack) > > >0x5AB4C () > > >0x5AA34() > > > > > >Why would the OS cause itself a bus error? What might be happening in my > > >app to have this outcome?
This could be in the runtime library too... I'd suggest finding the project which builds the runtime libraries, turning on debugging for that project, rebuilding the libs, and debugging with that project open (along with your original project). This way, CW will be able to source-level debug the runtime as well as your project. Maybe this will provide more insight. (BTW, what version of CW for Palm OS are you using? If its V7, make sure you've replaced the MSL Runtime libraries from the 4.0 SDK update with the ones that shipped in CW, as otherwise, you're using the V6 libs that won't always work correctly.) -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
