Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable providing fuzz targets using absolute paths #341

Merged
merged 1 commit into from
Feb 23, 2023

Conversation

kyakdan
Copy link
Member

@kyakdan kyakdan commented Feb 23, 2023

No description provided.

@kyakdan kyakdan added this pull request to the merge queue Feb 23, 2023
Merged via the queue into main with commit 7c6129f Feb 23, 2023
@kyakdan kyakdan deleted the FUZZ-600_absolute_paths branch February 23, 2023 09:07
oliverchang pushed a commit to google/oss-fuzz that referenced this pull request Feb 24, 2023
This fixes the issue of running Jazzer.js fuzzer using an absolute path
such as `/out/fuzzer`.

@oliverchang We needed a minor fix in Jazzer.js
(CodeIntelligenceTesting/jazzer.js#341), so you
would need to rebuild the project so that the latest version (1.4.0) is
fetched from npm.
eamonnmcmanus pushed a commit to eamonnmcmanus/oss-fuzz that referenced this pull request Mar 15, 2023
…9788)

This fixes the issue of running Jazzer.js fuzzer using an absolute path
such as `/out/fuzzer`.

@oliverchang We needed a minor fix in Jazzer.js
(CodeIntelligenceTesting/jazzer.js#341), so you
would need to rebuild the project so that the latest version (1.4.0) is
fetched from npm.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants