Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: Update ossfuzz stuff to clang-12+
Date: Wed, 16 Jul 2025 15:21:18 +0200
Message-ID: <20250716132118.GU29660@pb2> (raw)
In-Reply-To: <05b0fe3d-ba9d-49a1-873c-145dbb657a63@frankplowman.com>


[-- Attachment #1.1: Type: text/plain, Size: 2163 bytes --]

Hi

On Wed, Jul 16, 2025 at 11:11:13AM +0100, Frank Plowman wrote:
> 
> 
> On 16/07/2025 18:58, Kacper Michajlow wrote:
> > On Tue, 15 Jul 2025 at 00:24, Michael Niedermayer
> > <michael@niedermayer.cc> wrote:
> >>
> >> ---
> >>  configure | 4 ++--
> >>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/configure b/configure
> >> index fc082d5467e..e568eed55d3 100755
> >> --- a/configure
> >> +++ b/configure
> >> @@ -4606,8 +4606,8 @@ set >> $logfile
> >>  test -n "$valgrind" && toolchain="valgrind-memcheck"
> >>
> >>  enabled ossfuzz && ! echo $CFLAGS | grep -q -- "-fsanitize="  && ! echo $CFLAGS | grep -q -- "-fcoverage-mapping" &&{
> >> -    add_cflags  -fsanitize=address,undefined -fsanitize-coverage=trace-pc-guard,trace-cmp -fno-omit-frame-pointer
> >> -    add_ldflags -fsanitize=address,undefined -fsanitize-coverage=trace-pc-guard,trace-cmp
> >> +    add_cflags  -fsanitize=fuzzer,address,undefined -fsanitize-memory-track-origins -fno-omit-frame-pointer
> >> +    add_ldflags -fsanitize=address,undefined
> >>  }
> > 
> > How about we remove this block of code? Or move it to
> > --toolchain=clang-fuzz for local build? In oss-fuzz build environment
> > (docker) this flags shouldn't be injected (and are not because of grep
> > checks) and instead CFLAGS are used for compile flags and
> > --libfuzzer for linking.
> > 
> > - Kacper
> 
> +1
> 
> I have a patch locally which does something similar.  We could add these
> flags only to those targets which need to be compiled with libfuzzer,
> rather than to all CFLAGS.  It saves you having to re-configure if you
> want to compile some fftool, then some fuzzer binary or vice-versa.

I expect that the code a bug is in needs to be build with the sanitizer and
related flags. And that anything that we want fuzzed needs the fuzzer and
related flags

So that basically means everything needs these flags
IIUC in fact even external libs would need them

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are best at talking, realize last or never when they are wrong.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  parent reply	other threads:[~2025-07-16 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 22:24 Michael Niedermayer
2025-07-16  9:58 ` Kacper Michajlow
2025-07-16 10:11   ` Frank Plowman
2025-07-16 11:49     ` Frank Plowman
2025-07-16 13:21     ` Michael Niedermayer [this message]
2025-07-16 13:26   ` Michael Niedermayer
2025-07-17  1:16     ` Kacper Michajlow

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=20250716132118.GU29660@pb2 \
    --to=michael@niedermayer.cc \
    --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