Markakd/GREBE

Empty WorkSeed Error

Closed this issue · 9 comments

Hello,
After all the necessary installation steps, I start to run the grebe fuzzer. However, from the debug log, I encounter an error with the hint "panic: Empty WorkSeed!". As a result, the fuzzing processes are always be interrupted and no executions from the debug output. I worked through the source codes and found the length of the variable r.ProgSeed is zero and the branch with the hint "Received seed prog" did not have been executed. Further and farthest, I found the code "r := &rpctype.ConnectRes{}" do return the empty to r. So the panic is correct? I'm confused with this part. Could you please help to identify the problem I met?
Thanks for your help.

Hello, would you mind sharing the building process of analyzer component? There are some problems in my building.

@1120161891 , did you try to install llvm-10 before building the analyzer?

@1120161891 , did you try to install llvm-10 before building the analyzer?

yes, I installed llvm-10 before building.

Can you check if the LLVM path aligns with this file? If not, please adjust it accordingly.

If they are aligned and it still fails, can you send me the logs of building the analyzer?

Yes, the version should match. Otherwise the analyzer will not recognize the bitcode.

Hello, After all the necessary installation steps, I start to run the grebe fuzzer. However, from the debug log, I encounter an error with the hint "panic: Empty WorkSeed!". As a result, the fuzzing processes are always be interrupted and no executions from the debug output. I worked through the source codes and found the length of the variable r.ProgSeed is zero and the branch with the hint "Received seed prog" did not have been executed. Further and farthest, I found the code "r := &rpctype.ConnectRes{}" do return the empty to r. So the panic is correct? I'm confused with this part. Could you please help to identify the problem I met? Thanks for your help.

Did you solve this problem, I have the same problem.

@De4dCr0w @Markakd @1120161891 Hello, the problem is the missing of one command option. To start fuzzing, the command should be like "./bin/syz-manager -config=my.cfg -auxiliary=poc.txt", where the poc.txt is the syzkaller reproducer codes. For example, https://syzkaller.appspot.com/text?tag=ReproSyz&x=12f8067fe00000.