id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
256	LIBC stream fmutex panic	dmik	Silvan Scherrer	"An attempt to terminate a multi-threaded console program with Ctrl-C may often cause LIBC to abort with a message like this:
{{{
LIBC PANIC!!
fmutex deadlock: Owner died!
0x18b0902c: Owner=0x01490002 Self=0x01490001 fs=0x3 flags=0x0 hev=0x0001004a
            Desc=""LIBC stream""
pid=0x0149 ppid=0x00ba tid=0x0001 slot=0x00ba pri=0x0200 mc=0x0000
D:\CODING\TESTS\OS2\DOS\SEH\SEH.EXE
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.
}}}

This happens when a thread gets killed (as a result of the process termination procedure, initiated by the default Ctrl-C handler) while it is inside e.g. printf() and then another thread attempts to use printf() before it is terminated.

The same effect may be also seen when killing process with DosKillProcess.

This is very annoying (especially if there are many threads each of which panics) and it can also cause a hard deadlock (e.g. if printf() is used in an exception handler) that won't ever let thread 1 to exit."	defect	closed	normal	libc-0.6.6	libc	0.6.4	normal	fixed