On Tue, 18 May 2010, Mindaugas Kavaliauskas wrote: Hi,
> 3 similar samples with different error, so, perhaps we have memory > corruption here. This is expected and documented few times on this list behavior. Of course it's a bug but it cannot be well fixed without very serious modifications in RDD code and all code (also 3-rd part one) which access any RDD methods. It's necessary to introduce sth like: pArea = hb_rddLockCurrentArea(); [...] // any RDD methods hb_rddFreeArea( pArea ); hb_rddLockCurrentArea()/hb_rddLockArea(iArea) will increase reference counter and hb_rddFreeArea() will decrease it. non zero reference counter will delay releasing the pArea structure until hb_rddFreeArea() will set it to 0. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
