From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] gdigrab: Allow capturing a window by its handle
Date: Thu, 14 Dec 2023 12:52:48 +0200
Message-ID: <1C1177B2-2AA2-4AF3-A635-5B1DC6DA612A@remlab.net> (raw)
In-Reply-To: <ZXmBi81GtakwsWXB@phare.normalesup.org>
Le 13 décembre 2023 12:03:55 GMT+02:00, Nicolas George <george@nsup.org> a écrit :
>Rémi Denis-Courmont (12023-12-12):
>> ...and test for overflow errors in errno.m (which shall have been
>> zeroed beforehand). AFAIK, you need to do both if you want strict
>> error detection.
>
>Or we can consider that 30064771114 is just another valid way if writing
>42 = 042 = 0x2a. It would be better to check, but it is less critical
>than checking for garbage at the and, which itself is less critical than
>checking that the number is entirely absent.
That's completely arbitrary, TBH. Both cases are syntax errors, and there are no particular reasons to tolerate one but not the other. And even if it constitued a sensible distinction, that's simply not how strtoul() handles overflow: it returns ULONG_MAX, not a wrapped-around value.
In this case, both error cases are strong signs of a typing error or corruption.
_______________________________________________
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-12-14 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 22:10 [FFmpeg-devel] [PATCH] " Lena via ffmpeg-devel
2023-12-11 0:34 ` Andreas Rheinhardt
2023-12-11 1:35 ` Lena via ffmpeg-devel
2023-12-11 1:52 ` Lena via ffmpeg-devel
2023-12-12 0:47 ` Stefano Sabatini
2023-12-12 13:59 ` [FFmpeg-devel] [PATCH v2] " Lena via ffmpeg-devel
2023-12-12 14:07 ` Nicolas George
2023-12-12 15:31 ` Rémi Denis-Courmont
2023-12-13 10:03 ` Nicolas George
2023-12-14 10:32 ` [FFmpeg-devel] [PATCH v3] " Lena via ffmpeg-devel
2023-12-16 15:31 ` Stefano Sabatini
2023-12-17 17:29 ` [FFmpeg-devel] [PATCH v4] " Lena via ffmpeg-devel
2023-12-17 18:17 ` Stefano Sabatini
2023-12-14 10:52 ` Rémi Denis-Courmont [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=1C1177B2-2AA2-4AF3-A635-5B1DC6DA612A@remlab.net \
--to=remi@remlab.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