From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavu: make av_get_media_type_string() never return NULL
Date: Tue, 1 Feb 2022 19:34:48 -0300
Message-ID: <bdae01aa-d492-be3e-3dd3-6c4bafd7d5f3@gmail.com> (raw)
In-Reply-To: <20220201223058.31090-1-scott.the.elm@gmail.com>
On 2/1/2022 7:30 PM, Scott Theisen wrote:
> printf %s with a null pointer is undefined behavior
> ---
> libavutil/avutil.h | 3 +--
> libavutil/utils.c | 3 ++-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libavutil/avutil.h b/libavutil/avutil.h
> index 4d633156d1..4bd468d72f 100644
> --- a/libavutil/avutil.h
> +++ b/libavutil/avutil.h
> @@ -207,8 +207,7 @@ enum AVMediaType {
> };
>
> /**
> - * Return a string describing the media_type enum, NULL if media_type
> - * is unknown.
> + * Return a string describing the media_type enum, never NULL.
This is an API breakage, so it's not ok.
The doxy states it returns NULL if media_type is unknown, so you're
expected to check the returned pointer before trying to use it.
> */
> const char *av_get_media_type_string(enum AVMediaType media_type);
>
> diff --git a/libavutil/utils.c b/libavutil/utils.c
> index ea9b5097b8..c85d7abace 100644
> --- a/libavutil/utils.c
> +++ b/libavutil/utils.c
> @@ -71,12 +71,13 @@ const char *avutil_license(void)
> const char *av_get_media_type_string(enum AVMediaType media_type)
> {
> switch (media_type) {
> + case AVMEDIA_TYPE_UNKNOWN: return "unknown";
> case AVMEDIA_TYPE_VIDEO: return "video";
> case AVMEDIA_TYPE_AUDIO: return "audio";
> case AVMEDIA_TYPE_DATA: return "data";
> case AVMEDIA_TYPE_SUBTITLE: return "subtitle";
> case AVMEDIA_TYPE_ATTACHMENT: return "attachment";
> - default: return NULL;
> + default: return "invalid";
> }
> }
>
_______________________________________________
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-02-01 22:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 22:30 Scott Theisen
2022-02-01 22:34 ` James Almer [this message]
2022-02-02 1:58 ` Scott Theisen
2022-02-02 2:06 ` James Almer
2022-02-02 2:42 ` Scott Theisen
2022-02-02 2:13 ` Andreas Rheinhardt
2022-02-23 7:52 ` Anton Khirnov
2022-02-28 21:06 ` Scott Theisen
2022-02-03 20:09 ` [FFmpeg-devel] [PATCH v2] create av_media_type_get_string() Scott Theisen
2022-02-03 20:09 ` [FFmpeg-devel] [PATCH 1/2] libavutil: " Scott Theisen
2022-02-03 20:09 ` [FFmpeg-devel] [PATCH 2/2] replace av_get_media_type_string() with av_media_type_get_string() Scott Theisen
2022-02-13 21:52 ` [FFmpeg-devel] [PATCH v3] create av_media_type_get_string() Scott Theisen
2022-02-13 21:52 ` [FFmpeg-devel] [PATCH v3 1/2] libavutil: " Scott Theisen
2022-02-13 21:52 ` [FFmpeg-devel] [PATCH v3 2/2] av_get_media_type_string(): replace with av_media_type_get_string() Scott Theisen
2022-05-15 19:55 ` [FFmpeg-devel] [Patch v4 0/2] create av_media_type_get_string() Scott Theisen
2022-05-15 19:55 ` [FFmpeg-devel] [PATCH v4 1/2] libavutil: " Scott Theisen
2022-05-15 19:55 ` [FFmpeg-devel] [PATCH v4 2/2] av_get_media_type_string(): replace with av_media_type_get_string() Scott Theisen
2022-06-01 19:22 ` [FFmpeg-devel] [PATCH] " Scott Theisen
2022-09-16 17:32 ` [FFmpeg-devel] [PATCH v2] " Scott Theisen
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=bdae01aa-d492-be3e-3dd3-6c4bafd7d5f3@gmail.com \
--to=jamrial@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