Hi Kevin, thanks for your investigation.
Kevin B. Hendricks wrote:
I think that adding synchronization in module.c patch is just fine here. There is nothing global being used in the code as far as I can tell that would prevent it from being re-entrant. So the calls to NSAddImage which are internal MacOSX routines must be the culprit here.
Strange only that Apple doesn't document that this API is not thread-safe or is it just a bug ;-) Strange also that so far nobody reported problems I would expect without Patricks patch.
I would go ahead and commit the change since it can do no damage.
Well unnecessary locking is surely not helpful in the context of performance.
Kind regards, Tino --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
