It's a known problem that a DLL done in FPC has it's own memory
manager unless you do certain additional things to unify the memory
managers of the DLL and the main program. This is known to create at
least heap memory holes just wen passing strings between the main
program and the DLL. Maybe if using TThread this hits even "automatically".
But as a C DLL does not use Delphi strings nor TThread and needs to use
it's own heap, anyway, I suppose the problem is not related.
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
