Displaying 3 results from an estimated 3 matches for "handle_abort".
2015 Sep 05
3
Some feedback on Libfuzzer
...gt;
> Also, one more thing, currently Libfuzzer does not catch SIGABRT and
> treat it as a fatal event. I've added a SIGABRT handler to my own code
> and moved StaticDeathCallback to public so I can call it from there.
>
> Again, this is asan, not libFuzzer.
You need ASAN_OPTIONS=handle_abort=1
I hope to make it the default soon-ish.
> --
> greg
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML atta...
2015 Sep 08
2
Some feedback on Libfuzzer
...ibfuzzer does not catch SIGABRT and
> >> treat it as a fatal event. I've added a SIGABRT handler to my own code
> >> and moved StaticDeathCallback to public so I can call it from there.
> >>
> > Again, this is asan, not libFuzzer.
> > You need ASAN_OPTIONS=handle_abort=1
> > I hope to make it the default soon-ish.
>
> Ah, that would have made this work a bit simpler. Thanks.
>
> I have yet to really experiment with the sanitizers so I don't know if
> asan is really doing anything for me given Postgres's internal memory
> management...
2015 Sep 05
3
Some feedback on Libfuzzer
HI think I have a fairly nicely integrated Libfuzzer based fuzzer in
Postgres now. I can run things like:
SELECT fuzz(100000,'select regexp_matches(''foo/bar/baz'',$1,''g'')')
Which makes it convenient to fuzz arbitrary public functions available
in SQL. (I haven't figured out what interface to make for fuzzing
internal functions which take char