id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
152	libc: lost signals / thread pokes	bird	bird	It seems that we lose DosKillThread signals sometimes. I don't know why, but currently suspect DosOpen or something else in the fopen() sequence. For kLIBC 0.7 this will be solved by defining a 'kernel' and check for pending signals when exiting it. For kLIBC 0.6.2 adding a simple check for this condition fo the must-complete variant of fmutex seems to work around the problem well enough.	defect	closed	normal	libc-0.6.2	libc-backend	0.6	normal	fixed	DosKillThread lost signals