From: Marvin Scholz <epirat07-at-gmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/4] fftools/textformat: infer type in mermaid_print_value Date: Thu, 12 Jun 2025 13:34:02 +0200 Message-ID: <176A57A6-3641-4C87-B427-BA6091EBB464@gmail.com> (raw) In-Reply-To: <DM8P223MB0365FE6884FC5E5307D0AC80BA74A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On 12 Jun 2025, at 4:19, softworkz . wrote: > Hi Marvin, > >> -----Original Message----- >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of >> Marvin Scholz >> Sent: Mittwoch, 11. Juni 2025 21:57 >> To: ffmpeg-devel@ffmpeg.org >> Subject: [FFmpeg-devel] [PATCH 3/4] fftools/textformat: infer type in >> mermaid_print_value >> >> Instead of the caller having to indicate if it is passing an >> integer, just use the fact that str is NULL when an integer is >> to be printed. >> --- >> fftools/textformat/tf_mermaid.c | 12 ++++++------ >> 1 file changed, 6 insertions(+), 6 deletions(-) >> >> diff --git a/fftools/textformat/tf_mermaid.c >> b/fftools/textformat/tf_mermaid.c >> index dbe489a7a7..da371c8fff 100644 >> --- a/fftools/textformat/tf_mermaid.c >> +++ b/fftools/textformat/tf_mermaid.c >> @@ -547,7 +547,7 @@ static void >> mermaid_print_section_footer(AVTextFormatContext *tfc) >> } >> >> static void mermaid_print_value(AVTextFormatContext *tfc, const char >> *key, >> - const char *str, int64_t num, const >> int is_int) >> + const char *str, int64_t num) >> { >> MermaidContext *mmc = tfc->priv; >> const AVTextFormatSection *section = tf_get_section(tfc, tfc- >>> level); >> @@ -587,7 +587,7 @@ static void >> mermaid_print_value(AVTextFormatContext *tfc, const char *key, >> switch (mmc->diagram_config->diagram_type) { >> case AV_DIAGRAMTYPE_GRAPH: >> >> - if (is_int) { >> + if (!str) { > > This is not right - it would print 0 when the str is NULL. > See tf_xml, it uses the same pattern (is_int). > So what do you expect to happen when it is NULL? From what I have seen passing NULL for str would make these functions actually UB as passing NULL for a string to printf like functions is not defined, unless I missed this being handled explicitly somewhere. > Thanks, > sw > > _______________________________________________ > 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". _______________________________________________ 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:[~2025-06-12 11:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-11 19:57 [FFmpeg-devel] [PATCH 1/4] fftools/textformat: fix writing integers for mermaid Marvin Scholz 2025-06-11 19:57 ` [FFmpeg-devel] [PATCH 2/4] fftools/textformat: exit early in mermaid_print_value Marvin Scholz 2025-06-12 2:08 ` softworkz . 2025-06-11 19:57 ` [FFmpeg-devel] [PATCH 3/4] fftools/textformat: infer type " Marvin Scholz 2025-06-11 21:20 ` softworkz . 2025-06-12 2:19 ` softworkz . 2025-06-12 11:34 ` Marvin Scholz [this message] 2025-06-12 16:40 ` softworkz . 2025-06-11 19:57 ` [FFmpeg-devel] [PATCH 4/4] fftools/textformat: remove leftover comments " Marvin Scholz 2025-06-12 2:20 ` softworkz . 2025-06-12 2:04 ` [FFmpeg-devel] [PATCH 1/4] fftools/textformat: fix writing integers for mermaid softworkz .
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=176A57A6-3641-4C87-B427-BA6091EBB464@gmail.com \ --to=epirat07-at-gmail.com@ffmpeg.org \ --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