From: "Wujian(Chin)" <wujian2@huawei.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] 答复: [PATCH] fftools/ffmpeg_ffplay_ffprobe_cmdutils: add -mask_url to replace the protocol address in the command with the asterisk (*) Date: Wed, 28 Dec 2022 08:04:39 +0000 Message-ID: <f4f509372f6d416abce4bbee0f140da3@huawei.com> (raw) In-Reply-To: <20221227194913.GR3806951@pb2> >On Mon, Dec 26, 2022 at 01:07:51PM +0000, Wujian(Chin) wrote: >> The issue has been modified. Please review again, thank you! >> >> Signed-off-by: wujian_nanjing <wujian2@huawei.com> >> --- >> doc/fftools-common-opts.texi | 11 +++++++ >> fftools/cmdutils.c | 77 ++++++++++++++++++++++++++++++++++++++++++-- >> fftools/cmdutils.h | 25 ++++++++++++++ >> fftools/ffmpeg.c | 10 +++--- >> fftools/ffplay.c | 9 ++++-- >> fftools/ffprobe.c | 10 +++--- >> 6 files changed, 128 insertions(+), 14 deletions(-) >ffmpeg -h >segfaults with this patch >==32366== Invalid read of size 8 I have reproduced the problem. The reason is that the last element of argv_copy does not end with null. Otherwise, this problem will occur. Thanks. >==32366== at 0x30836B: split_commandline (in ffmpeg/ffmpeg_g) >==32366== by 0x3039CD: ffmpeg_parse_options (in ffmpeg/ffmpeg_g) >==32366== by 0x2ED201: main (in ffmpeg/ffmpeg_g) >==32366== Address 0x2ced5290 is 0 bytes after a block of size 16 alloc'd >==32366== at 0x4C33E76: memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) >==32366== by 0x4C33F91: posix_memalign (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) >==32366== by 0x116B322: av_malloc (in ffmpeg/ffmpeg_g) >==32366== by 0x116B4D8: av_mallocz (in ffmpeg/ffmpeg_g) >==32366== by 0x306469: copy_argv (in ffmpeg/ffmpeg_g) >==32366== by 0x306537: handle_arg_param (in ffmpeg/ffmpeg_g) >==32366== by 0x2ED1F5: main (in ffmpeg/ffmpeg_g) >==32366== > [...] >-- >Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB >Opposition brings concord. Out of discord comes the fairest harmony. >-- Heraclitus _______________________________________________ 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:[~2022-12-28 8:04 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-26 13:07 [FFmpeg-devel] " Wujian(Chin) 2022-12-26 13:21 ` Nicolas George 2022-12-27 19:49 ` Michael Niedermayer 2022-12-28 3:20 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-28 8:04 ` Wujian(Chin) [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-01-03 11:05 [FFmpeg-devel] " Wujian(Chin) 2023-01-03 12:31 ` Nicolas George 2022-12-21 10:10 [FFmpeg-devel] [PATCH] fftools/ffmpeg_ffplay_ffprobe_cmdutils:add " Wujian(Chin) 2022-12-22 19:28 ` Nicolas George 2022-12-23 7:14 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-23 9:13 ` Nicolas George 2022-12-23 11:04 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-23 11:06 ` Nicolas George 2022-12-19 13:15 [FFmpeg-devel] [PATCH] fftools/ffmpeg_ffplay_ffprobe_cmdutils: add " Wujian(Chin) 2022-12-19 13:30 ` Nicolas George 2022-12-19 13:37 ` Gyan Doshi 2022-12-19 13:44 ` Nicolas George 2022-12-20 11:42 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-22 19:27 ` Nicolas George 2022-12-24 8:51 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-24 8:59 ` Nicolas George 2022-12-19 13:33 ` [FFmpeg-devel] " Marvin Scholz 2022-12-19 13:37 ` Nicolas George 2022-12-19 13:40 ` Marvin Scholz 2022-12-19 13:45 ` Nicolas George 2022-12-20 11:56 ` [FFmpeg-devel] 答复: " Wujian(Chin) 2022-12-19 14:51 ` [FFmpeg-devel] " "zhilizhao(赵志立)" 2022-12-22 23:14 ` Marton Balint
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=f4f509372f6d416abce4bbee0f140da3@huawei.com \ --to=wujian2@huawei.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