From: softworkz <ffmpegagent@gmail.com> To: ffmpeg-devel@ffmpeg.org Cc: softworkz <softworkz@hotmail.com> Subject: [FFmpeg-devel] [PATCH] fftools/ffprobe: Disable stderr buffering on Windows Date: Sat, 19 Apr 2025 22:32:26 +0000 Message-ID: <pull.67.ffstaging.FFmpeg.1745101946780.ffmpegagent@gmail.com> (raw) From: softworkz <softworkz@hotmail.com> An identical call exists in ffmpeg.c With POSIX/glibc, stderr is already unbuffered (or line-buffered when a terminal is connected), but not in case of MSVCRT. Explicitly calling setvbuf() like in this commit, makes the Windows runtime behave like POSIX, giving the same “print immediately” behavior. Signed-off-by: softworkz <softworkz@hotmail.com> --- fftools/ffprobe: Disable stderr buffering on Windows An identical call exists in ffmpeg.c With POSIX/glibc, stderr is already unbuffered (or line-buffered when a terminal is connected), but not in case of MSVCRT. Explicitly calling setvbuf() like in this commit, makes the Windows runtime behave like POSIX, giving the same “print immediately” behavior. Signed-off-by: softworkz softworkz@hotmail.com Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-67%2Fsoftworkz%2Fsubmit_probe_nobuf-v1 Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-67/softworkz/submit_probe_nobuf-v1 Pull-Request: https://github.com/ffstaging/FFmpeg/pull/67 fftools/ffprobe.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c index f5c83925b9..d980d4e64f 100644 --- a/fftools/ffprobe.c +++ b/fftools/ffprobe.c @@ -3081,6 +3081,8 @@ int main(int argc, char **argv) init_dynload(); + setvbuf(stderr, NULL, _IONBF, 0); /* win32 runtime needs this */ + av_log_set_flags(AV_LOG_SKIP_REPEATED); options = real_options; base-commit: 7cd1edeaa410d977a9f1ff8436f480cb45b80178 -- ffmpeg-codebot _______________________________________________ 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".
reply other threads:[~2025-04-19 22:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pull.67.ffstaging.FFmpeg.1745101946780.ffmpegagent@gmail.com \ --to=ffmpegagent@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=softworkz@hotmail.com \ /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