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

xxcv xxcv07 at gmail.com
Fri Dec 11 11:39:22 CET 2009

Rémi Denis-Courmont wrote:
> On Thu, 10 Dec 2009 07:17:28 +1100, xxcv <xxcv07 at gmail.com> wrote:
>> ntkrnlpa.exe!KiUnexpectedInterrupt+0xbc
>> ntkrnlpa.exe!PsDereferencePrimaryToken+0x342
>> ntkrnlpa.exe!KiDeliverApc+0xb3
>> ntkrnlpa.exe!ZwYieldExecution+0x2570
>> ntkrnlpa.exe!NtWaitForSingleObject+0x9a
>> ntkrnlpa.exe!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb74
>> ntdll.dll!KiFastSystemCallRet
>> ntdll.dll!RtlEnterCriticalSection+0x46
>> msvcrt.dll!read+0x3d
>> libaccess_file_plugin.dll+0x1e76
> A crash within a system call seems a bit odd. That said, I don't know how
> Windows handles bad memory access within the kernel (Linux returns EFAULT,
> but maybe Windows makes the process crash).
> In any case, this report is unusable without a proper stack trace.
I can't it doesn't crash at all it simply freeze at the point of 2nd 
read() called 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.
I get really confused of the situation on winxp because it is possible 
in all kind of situations ... that I just described in mingw-w64 chat 
room. Its rather complex also I noticed I had sent this mail but it got 
delayed in to the mailing list for some reason, as well as I made reply 
regarding 1.0.4 release and also described my problem there but I didn't 
see it showing up in the mail list yet.

Best regards

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20091211/6a93499c/attachment.html>

More information about the vlc-devel mailing list