Skip to content

Several issues on running SCRepair #2

@sunbeomso

Description

@sunbeomso

Thanks for the answer in #1.

However, I still have problems on running SCRepair. Could you help me to run SCRepair?

[Q1] How to resolve the error message below?

Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 185, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/python3.8/runpy.py", line 111, in _get_module_details
    __import__(pkg_name)
  File "/home/sunbeom/SCRepair/CLI.py", line 4, in <module>
    from .IN import ProblemDetector, RepairCore, DetectedVulnerability, RepairTarget_Detector_Target, RepairTarget_Detector_Target_Remaining, RepairTarget_Detector_Target_Repaired, RepairTarget
ImportError: attempted relative import with no known parent package

I got this error message when I ran command python3.8 CLI.py repair test.sol.

[Q2] Are detectors (Oyente and Slither) expected to be installed using docker images?

I ask this question because the code in Slither.py seems to use Slither's docker image.
If not, on which program paths should these detectors be installed?

[Q3] Could you please provide more detailed instructions or examples on running SCRepair?

What values should be passed to the --detector flag?
(e.g., --detector Oyente?, --detector oyente?, or --detector Oyente_docker_container_ID?)

What values should be passed to the --targeted_vul flag?
(e.g., --targeted_vul integer_overflow?, --targeted_vul integeroverflow? or --targeted_vul IO?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions