Francois Piette wrote:
> Isn't it possible that the client is already destroyed when you call
> ThreadDetech ? If yes, accessing "self" in ThreadDetach cause the access
> violation.

Yes, very simple, that seems to be the reason. I think I've fixed it by
just waiting for all threads return and being freed manually in the main
thread before going ahead in the destructor.
Sometimes, when bugs are too obvious I don't find them :(

---
Arno Garrels [TeamICS]



-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to