As I said, I don't understand it. I just know that since I made that change, I am 100% stable again. I do not know the intimate details of the driver source though I (of-course) have looked at it and even use it (the binary) on occasion. I certainly haven't made it for ages! If you do find some underlying reason, I would appreciate knowing about it. But as an experiment, just comment out your Free() call when you do the malloc'ing and see what happens. Cheers Ben
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Beketov Danila Sent: May 29, 2007 9:41 AM To: [email protected] Subject: Re: Problem with function FreeARQualifierStruct ** But "driver" define qualifier in the same way (malloc), for example see function APIARGetListEntry in api.c, and FreeAR.. works without errors. Why ??? _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Ben Chernys Sent: Tuesday, May 29, 2007 11:16 AM To: [email protected] Subject: Re: Problem with function FreeARQualifierStruct Addendum: I might add that the results are also consistent (in their inconsistency at least) on a different OS and hardware platform. One in which I can trap buffer overwrites, double frees and the like on the instruction that they occur. (see ElectricFence - unfortunately, not available for Windows). The only thing I can think is that the API is adjusting addresses or playing with a cache of some sort when allocating and freeing some of its objects. I would certainly consider this a bug in the API (BMC: hint hint). Cheers Ben __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
