[FFmpeg-trac] #8917(undetermined:open): Exit on SIGPIPE or SIGHUP - "-xerror" not working as expected
FFmpeg
trac at avcodec.org
Wed Aug 10 01:50:04 EEST 2022
#8917: Exit on SIGPIPE or SIGHUP - "-xerror" not working as expected
-------------------------------------+-------------------------------------
Reporter: atom | Owner: (none)
Type: defect | Status: open
Priority: normal | Component:
| undetermined
Version: 4.2 | Resolution:
Keywords: sigpipe | Blocked By:
sighup error xerror |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by mldwrp):
Hi, I've asked the author of that commit (Mark Thompson) a question on
GitHub, but got no reply for two years.
I hope I'll have better luck here — as I'm updating my higher level
library at this moment — anyone is welcome to help.
@fhvwy Hello Mark,
Thank you for your work.
It so happens that this change has broken my
https://github.com/costa/ffmprb as it relies on an ability to distinguish
between pipe (IO) errors and other crashes.
Now, this change doesn't seem to me all that necessary, I usually follow
the "fail fast" philosophy (report and expect the upper layer to handle
failures) — it might benefit the end-user, but distinction between I/O
failures and others is apparently important for integration.
And I believe ffmpeg is mostly used in integrations where running few
processes in parallel is no problem (so each stream error can be reported
separately).
There is, however, a better way than reverting this change, and it's just
to report all I/O errors with a special exit code.
Thank you again.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8917#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list