[x264-devel] Suspect of a bug on x264 r2216 8-bit version (64-bit) for Windows

[Joshua Bowman]

On 10/17/2012 4:52 AM, Marco Vuano wrote:
> I'm still trying to get a proper back trace, in the meanwhile I attach Windows' error report.
> It seems that the error is in x264 and that the actual message is:
>
> "sh" non è riconosciuto come comando interno o esterno,
>
>  un programma eseguibile o un file batch.
>
> Which translates more or less into ""sh" is not recognized as an internal or external command,
> an executable program or a batch".
> Yours,
> Marco

Here's the quick and dirty way to get full core dumps on Windows:
In the registry, find HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting, create the key
LocalDumps, then create a string value DumpFolder with something like "C:\Temp" in it. Next time
something crashes, it'll go in there.

You might need Windbg for this, but I'm pretty sure you don't. The dump will be the same size as
the memory in use during the crash, so it could be huge. If it's too large to attach, you can
partially troubleshoot it yourself by installing Windbg, creating c:\symbols, selecting "Open
Crash Dump," then entering the commands:
    .sympath SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    .reload
    !analyze -v
Then email whatever comes out. You should get stack trace, thread list, more specific errors,
and so on. Full dump is definitely needed if that doesn't definitively point to the problem, though.

-- 
Joshua Bowman