Obviously one has to fix or workaround anything that halts Gremlins,
otherwise you can't use that automated testing tool.
I too was plagued by this warning, which doesn't appear to
be indicative of an fatal error in the code, but you never know!
(POSE with Palm OS 3.1 was my last experience). When it
occurs, it always occurs for me in setting up a form before
calling the draw function. I note that Nils is also using OS 3.1
I suspect it means that (for example) you're reading 30 bytes when
you only allocated 25. If you didn't allocate anything, you'd have a
NULL pointer and a very different problem.
If the (in example) 25 bytes contained a zero byte terminator, then
this overread would have no determental effect, but could be very
nasty if it didn't, hence the trap.
Can anyone offer guidance as to why this occurs, or how to further
deduce what it the fundamental problem?
Roger Stringer
Marietta Systems, Inc.
---------------------------------------------------------
>Subject: "Unallocated chunk"
>From: Nils =?ISO-8859-1?B?xQ==?=gren <[EMAIL PROTECTED]>
>Date: Sun, 05 Mar 2000 12:05:53 +0100
>Hello folks,
>I've been doing some testing with my app and POSE ( running a Palm V with
>various of memory settings (from 2048 - 8192 k). And after drawing a CharPtr
>on screen using WinDrawChars(...) it says "...has just read directly from am
>unallocated chunk of memory." But the memory handle, the CharPtr, is
>allocated, I get it from a textfield using following line:
>FldGetTextPtr( (FieldType*)FrmGetObjectPtr(frm, FrmGetObjectIndex(frm,
>THE_FIELD_RESOURCE_ID)));
>When using a real device ( a PalmV 2048 k) it works w/o any problems. Still,
>should I be worrying about the POSE problem?
>Thanks,
>Nils �gren
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
