>>So, my best guess is that your best guess is correct: it's an obscure bug of
>>your own (and you're finally running a version of Poser that detects it).
>
>:-) I was afraid you'd say that. I'd already spent quite a while looking
>for the problem, but failed to find anything suspicious in the code, so I
>was hoping for an arcane known issue with Poser. I'll keep staring at the
>code.
Why keep staring at code? USE A DEBUGGER! Poser gives you this nice error
dialog with a Debug button in it. CLICK ON IT! You'll be plopped in your
development environment's debugger right at the place where the infraction
occurs. Poke around there.
You say that the problem occurs in LstGetSelectionText? Getting the Palm OS
source code would help you match up the assembly code with the high-level
definition of the function.
Even if you don't or can't get the source code, LstGetSelectionText is a very
simple function. About the only way it could fail is if the list pointer is
invalid, or if itemNum is invalid (negative or too large). Take a look at those
values that the caller of LstGetSelectionText (your application) passed on the
stack.
Does itemNum look like it's valid? If so, then the problem must be with the
list pointer. Does it point to de-allocated memory? Dump the heap to find out.
If you're in CodeWarrior, go to the console window and use the "hd 0" command to
dump the heap. That should tell you where the allocated and free blocks are.
Does the list pointer point into a free block?
-- Keith Rollin
-- Palm OS Emulator engineer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
