Hmmm, you are right...
I noticed the Interlocked routine you are using is in "old interface"
(newer Delphi uses var parameters with which you do not need the @), any
chance that the seek procedure is located in another DLL and you are not
using FastMM?
Also, crashing inside memory allocation routine is likely to be caused by a
previous "double free".
.dlrow eht htiw thgir s'lla ,nevaeh sih ni si doG
From: "Ross Levis" <[EMAIL PROTECTED]>
Reply-To: Borland's Delphi Discussion List <[email protected]>
To: "'Borland's Delphi Discussion List'" <[email protected]>
Subject: RE: Threading issue
Date: Sun, 5 Aug 2007 18:12:39 +1200
The problem with that theory is that ReadBuf will not activate when
FBufferSize is 0, which it is after DeleteBuffers during a Seek. So a
WriteBuf must be executed first before a ReadBuf will do anything.
Therefore they should always be accessing different buffers.
Thanks,
Ross.
_________________________________________________________________
与世界各地的朋友进行交流，免费下载 Live Messenger;
http://get.live.com/messenger/overview
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
