-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
error: open k json file fail: ~/SyzDescribe/config/knowledge-v6.1.json #5
Comments
As mentioned,
This is the path of the knowledge file. |
I am sorry, I still can not find where the problem is, my knowledge json file is obtained from the repo and used in the way as mentioned above :
I would like to know, assuming there is a |
I find that you use The cmd should be
|
Thank you for the reply. In my environment, replacing the
|
Hi, an interesting job!
When I try to run SyzDescribe, I get some error.
My command is
tools/SyzDescribe/SyzDescribe --config_json=config.json
The info in
config.json
is:My linux kernel version download with the command
git clone --branch v6.1 xxx
My LLVM version "Ubuntu LLVM version 14.0.0", and clang version is
Ubuntu clang version 14.0.0-1ubuntu1.1
The info in
debug.log
is:I built the linux kernel v6.1 followed the command https://github.com/ZHYfeng/Generate_Linux_Kernel_Bitcode/blob/master/v6.1/README.md , and the build-in.bc files generated from the kernel source are present in each driver folder. I am not quite clear about the structural relationship between .bc, config.json, and the paths specified in config.json, and is there any difference in running Syzdescribe between linux kernel v6.1 and v6.2. I hope it can provide the absolute path relationships for script execution, or a demo example running with Syzdescribe.
Thanks.
In addition, when I run the command
build/tools/DifuzeFix/DifuzeFix --bitcode=built-in.bc
followed the https://github.com/ZHYfeng/PortedDIFUZE, I got the empty result.json file with the only "null" in it. Colud you give me some advice?The text was updated successfully, but these errors were encountered: