On 27 jun 2007, at 08:13, Vinzent Hoefler wrote:
There also seemed to be some issues with the reference counting: if I passed a local AnsiString to a thread constructor as argument and left the routine then, this seemed to confuse the thread throwing SIGSEGVs occasionally.
Maybe the parameter was declared as const? In that case, the refcount of the ansistring you pass isn't increased, because the compiler interprets the const as "the ansistring will not be changed in any way as long as that constructor is running". If it's a value parameter, it should work fine (a var parameter obviously wouldn't work either).
Jonas _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal