From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] ffprobe: restore reporting error code for failed inputs
Date: Wed, 17 Aug 2022 01:06:58 +0200
Message-ID: <20220816230658.GA3168@mariano> (raw)
In-Reply-To: <20220815183410.6741-1-ffmpeg@gyani.pro>
On date Tuesday 2022-08-16 00:04:10 +0530, Gyan Doshi wrote:
> c11fb46731 led to a regression whereby the return code for missing
> input or input probe is overridden by writer close return code and
> hence not conveyed in the exit code.
> ---
> fftools/ffprobe.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> Affects 5.1 so will need to be backported there.
>
> diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
> index ad633ccc44..8983dc28cc 100644
> --- a/fftools/ffprobe.c
> +++ b/fftools/ffprobe.c
> @@ -4032,7 +4032,7 @@ int main(int argc, char **argv)
> WriterContext *wctx;
> char *buf;
> char *w_name = NULL, *w_args = NULL;
> - int ret, i;
> + int ret, input_ret, i;
>
> init_dynload();
>
> @@ -4156,10 +4156,14 @@ int main(int argc, char **argv)
> show_error(wctx, ret);
> }
>
> + input_ret = ret;
> +
> writer_print_section_footer(wctx);
> ret = writer_close(&wctx);
> if (ret < 0)
> av_log(NULL, AV_LOG_ERROR, "Writing output failed: %s\n", av_err2str(ret));
> +
> + ret = FFMIN(ret, input_ret);
maybe we should give priority to input_ret in case they are both
negative?
return input_ret < 0 ? input_ret : ret;
?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-08-16 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 18:34 Gyan Doshi
2022-08-16 23:06 ` Stefano Sabatini [this message]
2022-08-17 4:12 ` Gyan Doshi
2022-08-17 7:07 ` Marton Balint
2022-08-17 7:13 ` Gyan Doshi
2022-08-17 11:19 ` Gyan Doshi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220816230658.GA3168@mariano \
--to=stefasab@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git