On Tue, 3 Apr 2012 09:51:59 +0200 Juan Jose Garcia-Ripoll <juanjose.garciarip...@googlemail.com> wrote:
> ... somehow these threads did not respond to the signal. I do not really > understand it. Was it before a change I did recently? ECL now _only_ blocks > its communication signal in sigsuspend(). It should not be blocking the > signal from the garbage collector. The issue started to occur when I imported your new changes after reading your message that started this thread (Message-ID: <canejtzqbreyz6dgpqxcvpktch+7dbjn+ldb7lg5qd8qk8wq...@mail.gmail.com>). The new implementation before that thread, including where you implemented a FIFO, were not blocking. Perhaps that the issue is with the GC, as it's similar, although much less random (this always locks now), than an older problem with the stable release ECL locks implementation... I could try to check the masks and signals of the threads the next time I give it a try. -- Matt ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
