Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Cannot collect MSVC compiled libfuzzer coverage #323

Closed
jopletchMSFT opened this issue Nov 18, 2020 · 0 comments · Fixed by #324
Closed

Cannot collect MSVC compiled libfuzzer coverage #323

jopletchMSFT opened this issue Nov 18, 2020 · 0 comments · Fixed by #324
Labels
bug Something isn't working

Comments

@jopletchMSFT
Copy link
Contributor

Information

  • Onefuzz version: 1.6.0
  • OS: Windows

Provide detailed reproduction steps (if any)

  1. Run a MSVC (16.8+) compiled libfuzzer target on OneFuzz

Expected result

A populated coverage dump in the coverage container

Actual result

Files containing 8 null bytes:

>xxd cov\xxx.exe.cov
00000000: 0000 0000 0000 0000
@jopletchMSFT jopletchMSFT added the bug Something isn't working label Nov 18, 2020
@ghost ghost added the Needs: triage label Nov 18, 2020
@jopletchMSFT jopletchMSFT mentioned this issue Nov 18, 2020
Merged
@bmc-msft bmc-msft linked a pull request Nov 18, 2020 that will close this issue
Fix MSVC Libfuzzer coverage reporting #324
Merged
@ghost ghost closed this as completed in #324 Nov 19, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix MSVC Libfuzzer coverage reporting
2 participants
@bmc-msft @jopletchMSFT