> >
> > POSE Error: "...directly read from data manager data structure.."
> >
> > Is this really a no-no? POSE identifies this as an error and I'm trying
> > to find the source.
> >
> > I have some code that gets Names from DB Records as follows:
> >
> > for(i=0; i<numRecs; i++) {
> > RecHandle = DmQueryRecord(MyDB, i);
> > RecPointer = MemHandleLock(RecHandle);
> > StrCopy(NameArray[i], RecPointer + 2); // name starts at +2
> > MemPtrUnlock(RecPointer);
> > }
> >
> > First, would this generate _that_ error?
> >
> > And second, is this a no-no? Why is that a no-no, if it is?
> >
> Is it possible that the string pointed to by RecPointer is not
> null-terminated? This would cause StrCopy to traipse off the end of the
> record and into the next record header, triggering a datamgr read error..
> Or, perhaps the record pointed to by RecPtr isn't even 3 chars long?
A couple of people have suggested this. But the error seems to
indicate that _any_ "direct reading of the Memory Manager Data
Sturcuture" would generate this error. It did not say anything about
reading past anything.
I'm not even sure that the code fragment is the source of the error.
I am just wondering:
1) what the error specifically means and
2) what can cause it.
I'm not trying to debug this particular code fragment.
These popup errors are not documented very well and it's a little
difficult to decypher them.
The one in question seems to indicate that _any_ direct read of the
Memory Manager Data Structure is a no-no.
Anyone know where one can get a translation of what these logged
errors actually mean?
>
>
>
> --
> Dan Rowley
> Innovative Computer Solutions
> Developers of fine software for Newton, Windows CE, Palm Computing
> Platform, Windows, and MacOS
>
--
-----------------------------------------------------------------
Discussion Group: http://www.halcyon.com/ipscone/wwwboard/
Protect your constitutional rights. Your favorite one may be next!
-----------------------------------------------------------------
