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
as does the following, which I broke out the eType to see why my app
still works if the eventP is really faulty.
Boolean LbsEnterFormHandleEvent(EventType * eventP)
{
Boolean handled= false;
FormType * frmP;
eventsEnum ThisEType = eventP->eType;
switch (ThisEType) <<<<<<<< stopped on this BP<<<<<<<<<<<<<<
{
case winEnterEvent:
.
.
.
When stopped on a BP on the "switch" line, the variable panel shows
ThisEType as = winEnterEvent, while showing eventP as all "invalid
pointers". I later noticed that eventP was in a register, and assumed
that the microcode was using the register for something else, while
internally keeping track of the value of eventP. I haven't written
microcode since VM370 days, so I figure anything's possible. i.e. Even
if this is kosher behavior for the CPU and not something that I have
done wrong, it's still pretty disconcerting.
Randyp
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
