[vlc-devel] Help read() 1.0-bugfix issue

Rémi Denis-Courmont remi at remlab.net
Fri Dec 11 18:12:51 CET 2009

On Fri, 11 Dec 2009 21:39:22 +1100, xxcv <xxcv07 at gmail.com> wrote:
> I can't it doesn't crash at all it simply freeze at the point of 2nd
> read() called

Ah, that makes more sense.

> and this call was never returned and I read from msdn
> website it described the entered critical section means it is waiting
> for file to be come ready.
> http://msdn.microsoft.com/en-us/library/ms682608%28VS.85%29.aspx


> I get really confused of the situation on winxp because it is possible
> in all kind of situations ...

Lets make things clear - a blocking can only happen in two cases:
The "normal" case involves VLC reading from a special file, e.g. a file on
a dead network share, a named pipe with only dead writers, a socket (but
not on Windows really), or a device file (e.g. CON, LPT1, COM1...).

If you see this with a local file, then you are in the abnormal case: your
operating system is just buggy and got stuck in a file system transaction,
or your hardware is failing.

But it might also simply be that VLC is stuck in *another* thread. In other
words, the stack trace is correct as such, but it does not show the correct

Rémi Denis-Courmont

More information about the vlc-devel mailing list