Skip to content
This repository has been archived by the owner on May 26, 2023. It is now read-only.

Bad return value #433

Open
mrx23dot opened this issue Jan 26, 2022 · 2 comments
Open

Bad return value #433

mrx23dot opened this issue Jan 26, 2022 · 2 comments

Comments

@mrx23dot
Copy link

mrx23dot commented Jan 26, 2022

Running
python /oyente/oyente/oyente.py --compilation-error -s /home/test.txt -b
test.txt

gives return value of 1 not 0, but result is valid:

WARNING:root:You are using evm version 1.8.2. The supported version is 1.7.3
WARNING:root:You are using solc version 0.4.21, The latest supported version is 0.4.19
INFO:symExec:   ============ Results ===========
INFO:symExec:     EVM Code Coverage:                     0.2%
INFO:symExec:     Callstack Depth Attack Vulnerability:  True
INFO:symExec:     Transaction-Ordering Dependence (TOD): False
INFO:symExec:     Timestamp Dependency:                  False
INFO:symExec:     Re-Entrancy Vulnerability:             False
INFO:symExec:   ====== Analysis Completed ======

echo $?

oyente version 0.2.7 - Commonwealth

@gsalzer
Copy link

gsalzer commented Jul 15, 2022

Oyente seems to return exit code 1 if a vulnerability is found, and 0 if none is detected. So the behavior you observe seems to be by design, not by error.

@mrx23dot
Copy link
Author

yeah, but if gcc would give non zero exit code on any warning none of the toolchains would work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants