On Wed, 16 Jul 2025 at 15:26, Michael Niedermayer
<mich...@niedermayer.cc> wrote:
>
> On Wed, Jul 16, 2025 at 11:58:14AM +0200, Kacper Michajlow wrote:
> > On Tue, 15 Jul 2025 at 00:24, Michael Niedermayer
> > <mich...@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
> > > }
> >
> > [...] Or move it to
> > --toolchain=clang-fuzz for local build?
>
> If you want to improve this, its welcome!
>
> note though this enables fuzzer+address+undefined theres also memory which
> cannot be enabled at the same time it seems (at least not when i tried)
> and needs a seperate build.
>
> so toolchain=clang-fuzz is a little to limited
> we need fuzz+address+undefined and fuzz+memory at least or something liek that
I've sent a patchset now to add support for multiple sanitizer
combinations and other QOL changes.
- Kacper
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
