From: David Korczynski <David@Adalogics.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Integrating GCC with oss-fuzz
Date: Mon, 16 Mar 2020 21:12:35 +0000 [thread overview]
Message-ID: <3657fb64-07b0-86a5-659b-5f2c5abaf426@adalogics.com> (raw)
Hi!
My name is David Korczynski and I have been doing some work on
integrating fuzzing by way of OSS-Fuzz into the gcc project. This came
out of fuzzing libiberty within the binutils project where we found
several bugs within libiberty. However, the binutils owners are not
working on libiberty so we dont get much results from reporting to them.
I was wondering if we could set up a similar project, namely by
integrating gcc to the OSS-Fuzz project and the errors found will then
automatically be sent to gcc-bugs@gcc.gnu.org? We can either add the
fuzzers upstream to gcc or do as binutils and adding them to OSS-Fuzz. I
have already done the work so we should be good to go with continuous
fuzzing if you are interested!
You can see the current binutils project here:
https://github.com/google/oss-fuzz/tree/master/projects/binutils
Here the binutils owners outline their interest in the project:
https://github.com/google/oss-fuzz/pull/2617
Kind regards,
David
next reply other threads:[~2020-03-16 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 21:12 David Korczynski [this message]
2020-03-17 10:25 ` Jonathan Wakely
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=3657fb64-07b0-86a5-659b-5f2c5abaf426@adalogics.com \
--to=david@adalogics.com \
--cc=gcc@gcc.gnu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).