Re: [Chicken-hackers] PATCH: allow signal handlers to be called from any thread.

2015-12-03 Thread Jörg F . Wittenberger
;-) as promised: Am 02.12.2015 um 14:57 schrieb Jörg F. Wittenberger: > No more patches today. This again is no good > because it allocates a slot in pending_interrupts, but doesn't - and > can't deallocate it. No more patches yesterday. This one sustained the test to sleep one night over it.

Re: [Chicken-hackers] PATCH: allow signal handlers to be called from any thread.

2015-12-03 Thread Jörg F . Wittenberger
Am 03.12.2015 um 14:01 schrieb John Cowan: > Jörg F. Wittenberger scripsit: > >> One more question. I would have expected chicken to store signals >> received while C_interrupts_enabled==0 and deliver them at some point >> after C_interrupts_enabled becomes true. Why are those signals ignored?

Re: [Chicken-hackers] PATCH: allow signal handlers to be called from any thread.

2015-12-03 Thread John Cowan
Jörg F. Wittenberger scripsit: > One more question. I would have expected chicken to store signals > received while C_interrupts_enabled==0 and deliver them at some point > after C_interrupts_enabled becomes true. Why are those signals ignored? That's what signal blocking is supposed to be