> >Has anyone seen this and know what I've got that's screwed up? (Win2k, > >CW9.1): > > > >The variable panel shows that the eventP variable is full of "invalid > >pointers", however, the usual code (...switch(eventp->eType)) works > fine
Optimizations are already full off, I usually don't start cranking them up until the code is nearly complete. Good Idea, though, Eric. > I've heard reports of this; my theory is that the debug info isn't > always > generated correctly for the EventType structure and that confuses the > debugger, but I've not been sent a reproducible case so that I can see > this > on my end and actually probe into the code <hint, hint> I'll send you the project, if you promise not to make fun =)) - it's less than half done and I haven't put much error handling, etc., in yet, so it's not much to look at... > > You can see where eventP is allocated by looking at the location > column. If you don't see it, turn it on using Edit/Preferences..., > Debugger/Display Settings, Show variable location. Then, if something's > allocated to a register, you'll see it's location as $A3 or similar. It is in a register, when it's screwed up.... as I single step back out to the event loop, the eventP display is fine again. As I mentioned, everything works fine, it just makes it hard to debug. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
