ffmpeg.exe on Windows does not respond properly to Ctrl+Break

[Joe Wreschnig]

In addition to SIGINT, on Windows it is common to send a different signal, SIGBREAK, which has similar effects. This can be triggered by pressing Ctrl+Break or by another process sending a signal.

New process groups on WIn32 usually ignore SIGINT; it is customary to stop a process in a separate process group by sending SIGBREAK.

The attached patch makes ffmpeg.exe respond to SIGBREAK in the same way it does SIGINT, using the WIndows console "control event" handler.

[Joe Wreschnig]

Patch against ~2012.06.18 git branch

[Carl Eugen Hoyos]

Please send patches to ffmpeg-devel, they receive more attention there.

[Roger Pack]

appears this wasn't "quite" committed yet...as of today anyway...http://web.archiveorange.com/archive/v/4q4BhNEWTcX2aCpF2IWz

[Carl Eugen Hoyos]

Replying to rogerdpack:

appears this wasn't "quite" committed yet...as of today anyway...http://web.archiveorange.com/archive/v/4q4BhNEWTcX2aCpF2IWz

If you want to push this patch, please resend a tested version to ffmpeg-devel. Posting a link (especially a non-working one) unfortunately does not help.

[Roger Pack]

See also ​http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=1133 which may be useful

[Carl Eugen Hoyos]

If you are interested in this issue please consider reading my last comment.

[Roger Pack]

(I would note also that ctrl+c [or sending the process the CTRL_C_EVENT] does/did already work, FWIW).

[Roger Pack]

OK finally got a commit in for this, thanks for the patch!