From: Steven Liu <lingjiujianke@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/encode: change the assert0 from (ret <= 0) to (ret >= 0)
Date: Tue, 28 Jun 2022 20:07:16 +0800
Message-ID: <CADxeRwkzK1AoH1+hujnJ4JCNjhdb7-9Uq_1Q6Ly1c9YphF8uXw@mail.gmail.com> (raw)
In-Reply-To: <DB6PR0101MB2214FEEA59645DD357A55CDA8FB89@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com>
Andreas Rheinhardt <andreas.rheinhardt@outlook.com> 于2022年6月28日周二 19:52写道:
>
> Steven Liu:
> > Because the codec->cb.encode return 0 is successed,
> > and the negative error code should failed.
> >
> > Signed-off-by: Steven Liu <lq@chinaffmpeg.org>
> > ---
> > libavcodec/encode.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavcodec/encode.c b/libavcodec/encode.c
> > index b68bf1e184..b43a16f708 100644
> > --- a/libavcodec/encode.c
> > +++ b/libavcodec/encode.c
> > @@ -217,7 +217,7 @@ static int encode_simple_internal(AVCodecContext *avctx, AVPacket *avpkt)
> > avpkt->pts = avpkt->dts = frame->pts;
> > }
> >
> > - av_assert0(ret <= 0);
> > + av_assert0(ret >= 0);
> >
> > emms_c();
> >
>
> You are asserting that encoding succeeds (and you allow encoders to
> return values > 0, which this check is meant to preclude). This is just
> wrong.
Should i only check succeeds !ret?
Thanks
Steven
_______________________________________________
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".
prev parent reply other threads:[~2022-06-28 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 11:50 Steven Liu
2022-06-28 11:52 ` Andreas Rheinhardt
2022-06-28 12:07 ` Steven Liu [this message]
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=CADxeRwkzK1AoH1+hujnJ4JCNjhdb7-9Uq_1Q6Ly1c9YphF8uXw@mail.gmail.com \
--to=lingjiujianke@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