Hi Matthias,
Resolved the issue.
Thank you,
Janardhan
On Thu, Jul 19, 2018 at 12:55 PM, Matthias Boehm wrote:
> Hi Janardhan,
>
> instead of continuing the discussion on the other thread of
> google/oss-fuzz, let us arrive at a project-wide conclusion first. As
> I said before, I don't think t
Hi Janardhan,
instead of continuing the discussion on the other thread of
google/oss-fuzz, let us arrive at a project-wide conclusion first. As
I said before, I don't think that creating fuzz tests for our native
kernels is a pressing issue right now because they only receive
internally constructe
We already received green signal. Yes, we qualify as a project with IT risk.
In last three days, I tried to reproduce most of the popular bugs such as
openssl-2014, and ran example builds for other projects on a docker to
understand fuzzing.
QUESTION:
I will try a simple fuzz target for now with
Well, in general this can be interesting. Apart from our default
testsuite, we occasionally ran static code analysis tools. Having
additional tests for partially valid scripts and inputs can help to
find more issues.
That being said, I don't think we currently qualify as a project with
"significan
They accepted( google/oss-fuzz ), SystemML project for fuzz testing.
PR link: https://github.com/google/oss-fuzz/pull/1429
- Janardhan
On Mon, May 21, 2018 at 11:46 AM, Janardhan wrote:
> Hi all,
>
>
> To find various programming errors (mostly detectable such as buffer
> overflow), a fuz
Hi all,
To find various programming errors (mostly detectable such as buffer
overflow), a fuzz testing can be of great help.
Merits:
1. It will easily detects common programming errors, which we might have
missed or not unit tested.
2. Improves the quality of our code.
---
Demerits:
1.
