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

Bug: Ctrl-C causes the fuzzer to store a "bug" violation #108

Open
OleksiiOleksenko opened this issue Jul 30, 2024 · 2 comments
Open

Bug: Ctrl-C causes the fuzzer to store a "bug" violation #108

OleksiiOleksenko opened this issue Jul 30, 2024 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@OleksiiOleksenko
Copy link
Contributor

Copied from @brianfu's PR:

Using "CTRL C" to cancel the run halfway will now cause it to spit out a "bug" violation for the canceled run (assuming this is to detect archfuzz bugs). Be careful to distinguish between actual architectural bugs and the false positives that are just testing artifacts.

@OleksiiOleksenko OleksiiOleksenko added the bug Something isn't working label Jul 30, 2024
@OleksiiOleksenko OleksiiOleksenko added this to the v1.3-hotfix milestone Jul 30, 2024
@OleksiiOleksenko OleksiiOleksenko self-assigned this Jul 30, 2024
@OleksiiOleksenko
Copy link
Contributor Author

@brianfu What was the command/config file necessary to reproduce this bug? (I can't reproduce with normal fuzzing)

@brianfu
Copy link
Contributor

brianfu commented Jul 30, 2024

I used this (with the bash variables set):

python $RVZR_DIR/revizor.py tfuzz -s $RVZR_DIR/base.json -n $TEST_PROGS -i $TEST_INPUTS -c $CFG_DIR/template_nonif.yaml -w $VIOL_DIR -t $CFG_DIR/template_VA.asm --nonstop &> $SCRIPT_DIR/output.out

I suspect this might be an artifact of things not perfectly being killed as a result of using --nonstop (The executor is killed but the python script keeps going); If so, it may not necessarily be a bug (or at least not one worth fixing).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants