From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavf: fall back to a more meaningful log instance name
Date: Mon, 03 Apr 2023 12:16:03 +0200
Message-ID: <168051696301.27013.16263636797264840578@lain.khirnov.net> (raw)
In-Reply-To: <20230402190635.GJ3542@mariano>
Quoting Stefano Sabatini (2023-04-02 21:06:35)
> On date Thursday 2023-03-30 11:38:07 +0200, Anton Khirnov wrote:
> > An uninitialized AVFormatContext instance with neither iformat nor
> > oformat set will currently log as 'NULL', which is confusing and
> > unhelpful. Print 'AVFormatContext' instead, which provides more
> > information.
> >
> > This happens e.g. if choosing an output format fails in
> > avformat_alloc_output_context2().
> > ---
> > libavformat/options.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavformat/options.c b/libavformat/options.c
> > index 22ad523b2d..e4a3aceed0 100644
> > --- a/libavformat/options.c
> > +++ b/libavformat/options.c
> > @@ -44,7 +44,7 @@ static const char* format_to_name(void* ptr)
> > AVFormatContext* fc = (AVFormatContext*) ptr;
> > if(fc->iformat) return fc->iformat->name;
> > else if(fc->oformat) return fc->oformat->name;
> > - else return "NULL";
> > + else return fc->av_class->class_name;
> > }
>
> Do you have an example to show? Anyway LGTM.
./ffmpeg -i /tmp/s.mkv -f foobar -y /dev/null
before: [NULL @ 0x5580377834c0] Requested output format 'foobar' is not a suitable output format
after: [AVFormatContext @ 0x55fa15bb34c0] Requested output format 'foobar' is not a suitable output format
--
Anton Khirnov
_______________________________________________
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:[~2023-04-03 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:38 Anton Khirnov
2023-03-30 9:38 ` [FFmpeg-devel] [PATCH 2/2] lavf/mux: clarify log messages when choosing oformat fails Anton Khirnov
2023-04-02 19:08 ` Stefano Sabatini
2023-04-02 19:06 ` [FFmpeg-devel] [PATCH 1/2] lavf: fall back to a more meaningful log instance name Stefano Sabatini
2023-04-03 10:16 ` Anton Khirnov [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=168051696301.27013.16263636797264840578@lain.khirnov.net \
--to=anton@khirnov.net \
--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