Skip to content

Provide further information when LibFuzzerMonitor fails to  #29

@pyoor

Description

@pyoor

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

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions