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.

Sign up for GitHub

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

Jump to bottom

NO new instrumentation output #53

Open
mineechor opened this issue Dec 16, 2022 · 2 comments
Open

NO new instrumentation output #53

mineechor opened this issue Dec 16, 2022 · 2 comments

Comments

@mineechor
Copy link

f79c201b733f7dcd7bced817ecef2e8
@stong
Copy link
Member

stong commented Dec 17, 2022 •
edited
Loading

Please provide more information, including:

  • System hardware configuration
  • OS configuration and version (from winver)
  • Test case
  • Full command line
  • Output from debug build and debug mode enabled

No new instrumentation output means that the test case does not hit any new basic blocks. This may be a result of normal operation, not a bug.

@mineechor
Copy link
Author

configuration：Windows 10 x64 version 10.0.19044
cpu Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz 6 cores
RAM 16GB
cmd:afl-fuzz -i in -o out -t 9000 -I 9000 -- -bbfile basicblocks.bb -- -harness harness.dll -no_minidumps -- photoviewer.exe @@
harness.zip
The file in harness.zip is used to generate harness.dll.
The output from debug mode is as followed.
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stong @mineechor