search

nevillegrech / gigahorse-toolchain

A binary lifter and analysis framework for Ethereum smart contracts
Other
295 stars 61 forks source link

Why is the compiled file incomplete? #53

Closed lwy0518 closed 1 year ago

lwy0518 commented 1 year ago

My souffle version is 2.1, and the file opened after running command "gigahorse-toolchain/gigahorse.py -C detector2.dl examples/long_running.hex" has very little content. The result is as follows: image image

Why not get complete data? Looking forward to your reply, thank you very much!

sifislag commented 1 year ago

Hi, Can you share the console output of gigahorse.py? Also you can try with souffle 2.3 and see if that makes a difference. Lastly it looks like the output is for a file named SimpleDAO and not long_running.

lwy0518 commented 1 year ago

First of all, thank you very much for your reply! Hi, sifis，I'm sorry. It may be that there is a problem with the compiled bytecode. I tried a file named long_runnig and the result is complete. But I have another question.There are many outputs(.output) A file named detector2.dl, but after running the command(gigahorse-toolchain/gigahorse.py -C detector2.dl examples/long_running.hex) sometimes these outputs are displayed and sometimes not. How can I solve this problem? image image Looking forward to your reply！

sifislag commented 1 year ago

Can you show me what gigahorse prints to the console in both cases (when outputs are missing and when they're there)?

lwy0518 commented 1 year ago

For distinction, all output results start with Vul_, but looking at a file named .temp/long_running/out/ does not have these. image image image