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.

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

Show currently fuzzed testcase to TUI #2757

Open
domenukk opened this issue Dec 11, 2024 · 4 comments · May be fixed by #2810
Open

Show currently fuzzed testcase to TUI #2757

domenukk opened this issue Dec 11, 2024 · 4 comments · May be fixed by #2810
Labels
good first issue Good for newcomers

Comments

@domenukk
Copy link
Member

For slower targets, the current cycle count is very very slow.
It'd be nice to instead see in the individual fuzzer's output (TUI) what testcase (corpus_idx) is currently scheduled.

@domenukk domenukk added the good first issue Good for newcomers label Dec 11, 2024
@tokatoka tokatoka changed the title Report currently fuzzed testcase Add currently fuzzed testcase to TUI Dec 13, 2024
@tokatoka tokatoka changed the title Add currently fuzzed testcase to TUI Show currently fuzzed testcase to TUI Dec 13, 2024
@devratapuri
Copy link

Hi @domenukk
I would love to take this issue .But, I am new to codebase can you guide me for above task.

@domenukk
Copy link
Member Author

The important part of this is to fire! an UpdateUserStats event:

UpdateUserStats {

from a stage, probably from the StatsStage:
let testcase = state.corpus().get(corpus_idx)?.borrow();

And then add that info to the TUI Monitor:

pub struct TuiMonitor {

@devratapuri
Copy link

Thanks @domenukk for explanation will try to resolve this

@devratapuri
Copy link

Hey @domenukk have tried to change according to steps you mentioned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants