> On the real Palm & on 3.0a4, it works fine.
No...it doesn't work just fine. It's just an undetected/unreported error.
On an actual device, you're not going to see the error reported since there is
no facility for detecting the error. Palm devices...well, heck, almost any
computing device, including Windows PCs, don't typically have the facilities for
detecting errant accesses to deallocated memory blocks. So I'm not really sure
why you're expecting anything. The error message you're getting is provided by
the Emulator, so you will see it only when running under it.
Also, you probably aren't seeing the error message under Poser 3.0a4 because
that's an old, inferior version. It's almost a year old. Naturally, there have
been lots of changes to Poser over the last year, including better error
detection and reporting. It's entirely possible that you are now seeing an
error message because of a bug fixed in 3.0a7, as documented in the following
_News.txt item:
* After creating a handle with MemHandleNew, locking it, remembering
the pointer, and then freeing the handle with MemHandleFree, the
application could write to the freed block using the now-stale
pointer. Fixed. [Neil Rhodes]
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). So I
suggest that the next time you see that error message, you click on the handy
"Debug" button in the dialog box and start tracking down what's going on. If
you find out more information and it doesn't look like a bug of yours, then
please come back and post that information here.
-- Keith Rollin
-- Palm OS Emulator engineer
Richard Sewell <[EMAIL PROTECTED]> on 11/23/2000 10:43:10 AM
Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent by: Richard Sewell <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
cc: (Keith Rollin/US/PALM)
Subject: POSE 3.0a7 problem with popup
I'm getting a problem with a popup category selector with POSE 3.0a7, but
not with 3.0a4 or with a real device.
The list pops up correctly, but as soon as an item on it is selected I see
the 'has just read directly from an unallocated chunk of memory' alert.
On the real Palm & on 3.0a4, it works fine.
Anyone seen anything like this before ? Is this an obscure bug of our own
or a known POSE artefact ?
Richard
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
