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

Provide further information when LibFuzzerMonitor fails to #29

Open
pyoor opened this issue Apr 10, 2024 · 0 comments
Open

Provide further information when LibFuzzerMonitor fails to #29

pyoor opened this issue Apr 10, 2024 · 0 comments

Comments

@pyoor
Copy link
Contributor

pyoor commented Apr 10, 2024

When the LibFuzzerMonitor fails to init, we have very little insight into what caused it. We should include the most recent parsed lines in the output.

Job 0 terminated, processing results...
Process did not startup correctly, aborting... (1)
[Job 1] Received terminate request...
[Job 1] ==668== libFuzzer: run interrupted; exiting
[Job 2] Received terminate request...
[Job 2] ==670== libFuzzer: run interrupted; exiting
[Job 3] Received terminate request...
[Job 3] ==673== libFuzzer: run interrupted; exiting

guided-fuzzing-daemon/src/guided_fuzzing_daemon/libfuzzer.py

Line 584 in eeb20af

"Process did not startup correctly, aborting... (1)",

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
1 participant
@pyoor