Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #3399 > unrolled thread

5333 array handling

Started byMartin <spam@spam.spam>
First post2012-05-03 10:07 +0100
Last post2012-05-04 00:27 -0700
Articles 2 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  5333 array handling Martin <spam@spam.spam> - 2012-05-03 10:07 +0100
    Re: 5333 array handling Mathias <mathias.hakansson@consultec.se> - 2012-05-04 00:27 -0700

#3399 — 5333 array handling

FromMartin <spam@spam.spam>
Date2012-05-03 10:07 +0100
Subject5333 array handling
Message-ID<xVror.288356$IU.177954@fx28.am4>
DYNINFOFREE:              4
DYNINFOMAX:               16777216
DYNINFOSIZE:              256
DYNINFOUSED:              16777212

Error was on a AAdd line, is this just increase DynInfoSize?

Thanks

Martin

[toc] | [next] | [standalone]


#3404

FromMathias <mathias.hakansson@consultec.se>
Date2012-05-04 00:27 -0700
Message-ID<16777693.600.1336116462901.JavaMail.geo-discussion-forums@vbjb10>
In reply to#3399
Hi Martin,

5333 means that the system has found currupted data in memory, typically the system has a pointer to an object, but the object is not there.

Increasing dyninfosize may make the error less likely to happen, but does not fix the real problem. Finding the real problen can be really hard. Geoff Shaller have written a very good article about this. I suppose you will find a link to it somewhere on this newsgroup if you do a search with the proper keywords...

/Mathias

Den torsdagen den 3:e maj 2012 kl. 11:07:50 UTC+2 skrev Martin:
> DYNINFOFREE:              4
> DYNINFOMAX:               16777216
> DYNINFOSIZE:              256
> DYNINFOUSED:              16777212
> 
> Error was on a AAdd line, is this just increase DynInfoSize?
> 
> Thanks
> 
> Martin

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web