It's amazing what reading your own post will do. I just thought, hey Dave, maybe try getting rid of the alert getting called on top of no window and seeing if it works then, and it did.
Which brings me to a more concise question: I've encountered weirdness before with alerts during startup before any form is loaded. Is this legal? I haven't been able to find any documentation on it. "David Eyler" <[EMAIL PROTECTED]> wrote in message news:105777@palm-dev-forum... > > Hi all, I've been struggling with this problem for awhile now with no luck, > so any insights will be greatly appreciated. > > What happens is that I'm running gremlins, and it leaves and re-enters my > app and goes to the event loop. I show a modal form and an alert before > calling FrmGoToForm(), and then it enters the event loop. First I get a > winExitEvent, which works fine, then I get a "read from unallocated error at > address 0x000064EE". > > So far I've only been able to reproduce this bug on the *release* roms (with > both debug and release targets), specifically palmos40-en-m505 and a 4.0.1 > ROM image from my own m125. I tried it with the palmos40-en-dbg-m505 ROM and > got no errors. > > The stack trace shows: > > PilotMain > StarterPalmMain > AppEventLoop > 0x10049400( SysEventGet ) > 0x10049400( SysEventGet ) > 0x1004FE04( WinSetDrawWindow ) > > The last instructions executed in assembly are > > 1004FE04: 22780122 movea.l 0x00000122,a1 > 1004FE08: 22690DD8 movea.l 3544(a1),a1 > 1004FE0C: 4E91 jsr (a1) > > but I admit that I don't know how to make any sense from the assembly. > > I looked at the source for WinSetDrawWindow, but couldn't find anything that > might cause that error except for WinValidateHandle() and BmpGetBits(), and > I tried calling both those functions with the current draw window right > before the EvtGetEvent() that was about to crash and they worked fine. > > Any ideas? > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
