You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm reaching out to ask if spirv-cross would be happy to integrate with OSS-Fuzz? OSS-Fuzz is a continuous fuzzing set up for important open source projects and has helped find a lot of memory corruption issues in various projects.
In google/oss-fuzz#12708 I did an initial integration of SPIRV-cross and would be happy to submit a further set of harnesses if you're happy to integrate. The goal would be to have good coverage of SPIRV-cross.
In order to integrate, the only thing needed is one or more maintainer emails that would be happy to receive notifications for any issues find, including detailed reports with stacktraces, reproducers and more. The project will also show up on https://introspector.oss-fuzz.com/ where it's convenient to track e.g. fuzzing code coverage of the projects in OSS-Fuzz.
The text was updated successfully, but these errors were encountered:
I don't have the bandwidth to stay on top of any process like this. Also, SPIRV-Cross is not intended to be robust against any garbage input. It is expected that input is valid SPIR-V.
This is a follow-up to #1238
I'm reaching out to ask if spirv-cross would be happy to integrate with OSS-Fuzz? OSS-Fuzz is a continuous fuzzing set up for important open source projects and has helped find a lot of memory corruption issues in various projects.
In google/oss-fuzz#12708 I did an initial integration of SPIRV-cross and would be happy to submit a further set of harnesses if you're happy to integrate. The goal would be to have good coverage of SPIRV-cross.
In order to integrate, the only thing needed is one or more maintainer emails that would be happy to receive notifications for any issues find, including detailed reports with stacktraces, reproducers and more. The project will also show up on https://introspector.oss-fuzz.com/ where it's convenient to track e.g. fuzzing code coverage of the projects in OSS-Fuzz.
The text was updated successfully, but these errors were encountered: