On 10/26/12 3:43 PM, Florent Hivert wrote:
Aside William's caveat, I would add "don't mix fork and threads". A more or less accurate description of what could happen is that forking is somehow not atomic so that you may end up forking also threads you don't want to. Before being aware of that I had some very nasty behavior such as a lock being taken twice by the same thread. I can imagine that it could leads to double frees...
I thought this article title was great: http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-using-them
"Threads and fork(): think twice before mixing them" The article itself is an interesting read. Thanks, Jason -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
