How to correctly generate .simresult file

[wynn1212]

Hi!
I have some trouble generating .simresult file
In the evaluation_set folder, each [Device name] folder have one firmware binary and alone with 2 simresult file which is [Device_name].simresult and [Device_name]_all.simresult

Take DIR-100 as an example, if I try to generate myself simresult file via unstrip.jar with this command.

java -jar build/libs/unstrip-1.0-SNAPSHOT.jar ../../30_DIR100/30_DIR100 -c -l MIPS:BE:32:default -b 0x80000100 -O ../../30_DIR100/30_DIR100.simresult

It'll generated the simresult file but in run.sh it'll end up did not find any source_func, therefore cannot generate findtrace_output result (only summary and summary.json) and it looks like it is missing some function name like Packt_WebGetsVar, recv and recvfrom

• So how to correctly generate the [Device name].simresult file?

• Also I have a question about how does [Device name]_all.simresult being generated?

Thank you!

Below is my self-generate simresult file via the unstrip.jar with the command above.
30_DIR100.simresult.txt
Which hope it helps to diagnosis the problem I have.

[zunlongzhou]

I am also troubled by the same problem. Have you solved it?

[Jianchun-Ding]

I am also troubled by the same problem. Have you solved it? @wynn1212 @zunlongzhou @bob777sjtu Thanks a lot!

[Kang-Sir-C]

I am also troubled by the same problem. Have you solved it?

Hello, can we get in touch and discuss the implementation of SFuzz?

[Kang-Sir-C]

Hi! I have some trouble generating .simresult file In the evaluation_set folder, each [Device name] folder have one firmware binary and alone with 2 simresult file which is [Device_name].simresult and [Device_name]_all.simresult

Take DIR-100 as an example, if I try to generate myself simresult file via unstrip.jar with this command.

java -jar build/libs/unstrip-1.0-SNAPSHOT.jar ../../30_DIR100/30_DIR100 -c -l MIPS:BE:32:default -b 0x80000100 -O ../../30_DIR100/30_DIR100.simresult

It'll generated the simresult file but in run.sh it'll end up did not find any source_func, therefore cannot generate findtrace_output result (only summary and summary.json) and it looks like it is missing some function name like Packt_WebGetsVar, recv and recvfrom

* So how to correctly generate the `[Device name].simresult` file?

* Also I have a question about how does `[Device name]_all.simresult` being generated?

Thank you!

Below is my self-generate simresult file via the unstrip.jar with the command above. 30_DIR100.simresult.txt Which hope it helps to diagnosis the problem I have.

Hello, I also encountered this problem. Do you have the implementation record of the dynamic analysis part of SFuzz? It would be better if it is a new firmware.

[N1nEmAn]

how to? i wanna know too

[N1nEmAn]

Hi! I have some trouble generating .simresult file In the evaluation_set folder, each [Device name] folder have one firmware binary and alone with 2 simresult file which is [Device_name].simresult and [Device_name]_all.simresult
Take DIR-100 as an example, if I try to generate myself simresult file via unstrip.jar with this command.

java -jar build/libs/unstrip-1.0-SNAPSHOT.jar ../../30_DIR100/30_DIR100 -c -l MIPS:BE:32:default -b 0x80000100 -O ../../30_DIR100/30_DIR100.simresult

It'll generated the simresult file but in run.sh it'll end up did not find any source_func, therefore cannot generate findtrace_output result (only summary and summary.json) and it looks like it is missing some function name like Packt_WebGetsVar, recv and recvfrom

* So how to correctly generate the `[Device name].simresult` file?

* Also I have a question about how does `[Device name]_all.simresult` being generated?

Thank you!
Below is my self-generate simresult file via the unstrip.jar with the command above. 30_DIR100.simresult.txt Which hope it helps to diagnosis the problem I have.

Hello, I also encountered this problem. Do you have the implementation record of the dynamic analysis part of SFuzz? It would be better if it is a new firmware.

now i know. run /root/SFuzz/static_analysis/extract_helper/ghidra.py in ghidra9.2.3