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

Command to reproduce the bug problem #3

Open
datadancer opened this issue Feb 5, 2021 · 1 comment
Open

Command to reproduce the bug problem #3

datadancer opened this issue Feb 5, 2021 · 1 comment

Comments

@datadancer
Copy link

Given that you have found a USB bug, you may need to reproduce the bug. Assume that we have found a bug and the crashing input is saved in bugs/bug1.

 run the following command to start the guest vm:

./usbfuzz-afl/qemu_mode/qemu-build/x86_64-softmmu/qemu-system-x86_64 -M q35 -device qemu-xhci,id=xhci -object memory-backend-shm,id=shm -device ivshmem-plain,id=ivshmem,memdev=shm -m 4G -enable-kvm -kernel OSes/linux-target/linux-test-build/arch/x86_64/boot/bzImage -hda images/linux/stretch.img -append 'root=/dev/sda console=ttyS0' -usbDescFile bugs/bug1 -serial stdio
The usbDescFile should be bugs/bug1, not seeds/usb_sk4Wm9j.

@wanrenmi
Copy link

I found some crash input in workdir/crashes. One of them is named "id:000000,sig:81,src:000025,op:flip2,pos:11".
But when I try to reproduce the bug, use the command like "xxxxx -usbDescFile workdir/crashes/id:000000,sig:81,src:000025,op:flip2,pos:11 stdio -serial stdio", it says "qemu-system-x86_64: -usbDescFile workdir/crashes/id:000000,sig:81,src:000025,op:flip2,pos:11: drive with bus=0, unit=0 (index=0) exists" and does not work. But when I use "-usbDescFile bugs/bug1", it can work. Is that because the crash input is incomplete or something else?

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

No branches or pull requests

2 participants