On Thu, Jan 20, 2011 at 12:31 PM, Anton Vodonosov <avodono...@yandex.ru>wrote:
>
> It's a good idea, thanks. I will only need to think about race conditions,
> like if GC starts after the sigwait returns, but before we called
> GC_register_my_thread. Or this code doesn't allocate any heap memory and
> should not be protected by GC?
>
>
Code in the library is itself protected, so one should not worry about it.
I just realized that there might be another problem. When ECL exits it tries
to do so in an organized way, sending a termination signal to each of the
threads. If the library does not allow the sigwait thread to be terminated,
ECL might just hang waiting for it.
Juanjo
--
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
