2.7.5 64-bit having strange crash

[dosdan]

I see that what you've put is a "find" utility.  But how am I supposed to know what to look for? 

As eumagga0x2a previously mentioned, search for (include the double inverted commas around the string):

"Reinit context to"

The command needed is:

ffplay -debug pict media_file_to_be_checked 2>&1 | find /i "Reinit context to"

As he mentioned (https://avidemux.org/smif/index.php/topic,18831.msg87195.html#msg87195), this string, when reported while operating in fflplay's debug mode, will be associated with the occurrence of an on-the-fly video resolution change:

Reinit context to 1088x624, pix_fmt: yuv420p

Dan.

[eumagga0x2a]

@dosdan:

Does it mean that the cmd.exe syntax for redirecting stderr to stdin is the same as in bash?

[dosdan]

@dosdan:

Does it mean that the cmd.exe syntax for redirecting stderr to stdin is the same as in bash?

Don't know bash.

cmd.exe has become fairly powerful these days:  https://ss64.com/nt/syntax-redirection.html

https://ss64.com/nt/

4DOS/4OS2/4NT/Total Command Console was and still is a more powerful command interpreter than either command.com or cmd.exe (https://en.wikipedia.org/wiki/4DOS)

[dosdan]

BTW, here's a GnuWin version of grep:

https://sourceforge.net/projects/gnuwin32/files/grep/2.5.1-2/grep-2.5.1-2-bin.exe/download

Window's FIND & FINDSTR may have problems in binary files due to "line length" limitations. This port of grep may be better in this regard.

Dan.

[eumagga0x2a]

I refer to 2>&1 part of the bash command line.

[dosdan]

I refer to 2>&1 part of the bash command line.

That's been in CMD for a long time, I think from the very start of Windows NT (1993).

The redirection of STDERR wasn't possible in DOS's command.com, but it was in 4DOS (1989) because that was modelled on unix.

Dan.

[eumagga0x2a]

Good to know, thanks.