wm4 e9e68fc399 msg: use a global lock to synchronize printing ... We have certain race conditions coming from doing multiple fprintf() calls (setting up colors etc.). I'm not sure whether it would be worth changing to code such that we do only one fprintf() call (and assume this synchronizes access), but considering it would be hard to do (Windows compatibility, ...), and that stdio uses per FILE locks anyway, this is simpler and probably not less efficient. Also, there's no problem handling the weird statusline special case this way. Note that mp_msg_* calls which are silent won't acquire the lock, and acquiring the lock happens on actual output only (which is slow and serialized anyway).		2013-12-20 21:07:58 +01:00
..
asxparser.c
asxparser.h
av_common.c
av_common.h
av_log.c
av_log.h
av_opts.c
av_opts.h
codecs.c
codecs.h
common.c
common.h
cpudetect.c
cpudetect.h
encode_lavc.c
encode_lavc.h
encode.h
global.h
msg.c	msg: use a global lock to synchronize printing	2013-12-20 21:07:58 +01:00
msg.h	msg: change --msglevel, reduce legacy glue	2013-12-20 21:07:57 +01:00
playlist_parser.c
playlist_parser.h
playlist.c
playlist.h
version.c