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? > > > > > >"Keith Rollin" <[EMAIL PROTECTED]> wrote in message > >news:81593@palm-dev-forum... > >> > >> Darren, > >> > >> Are you basing your statement that the error occurs inside > >> FrmCloseAllForms on the logging information below? Because that log > >> doesn't indicate when a function returns to the caller. Thus, the > >> error could be occurring in WinPopDrawState, FrmCloseAllForms, or > >> (since calling WinPopDrawState is the last thing FrmCloseAllForms > > > does) even in the routine that called FrmCloseAllForms. > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
