Skip to content

Is there any guidance to run a motivating example? #3

@xiaoguai0992

Description

@xiaoguai0992

Thanks for your work on automatic cause bisection for Linux kernel vulnerability. I believe it would facilitate the real-world debugging practice.

I am a little bit of confused about how to use this tool.

It seems that this repository only contains the "Symbolic Detector" module metioned in the paper. However, it seems to be not enough. It looks like that I have to build a symbolic execution guidance using "Guidance Generator" and align it to the target testing version using "Guidance Transformer". I have no idea of how to finish these steps. Also I am confused how should I fill the config.json. It is just empty in this repository. So how to trace the PoC on the reference and target version and how should I fill the parameters in config.json to bisect the motivating example in the paper?

Thank you once again, and I look forward to your response.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions