False Positive on Public Enums

Mythril 0.18.4 reports false positive on public enum storage variables.

pragma solidity ^0.4.19;

contract Benchmark {
    enum State {
        s1
    }
    State public state;
}

==== Exception state ====
Type: Informational
Contract: Unknown
Function name: _function_0xc19d93fb
PC address: 100
A reachable exception (opcode 0xfe) has been detected. This can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. This is acceptable in most situations. Note however that `assert()` should only be used to check invariants. Use `require()` for regular input checking. 
--------------------
In file: public_storage_enum.sol:7

State public state

--------------------
```

[rocky]

Here is a related thought regarding this. With interaction with static analysis we can know this is an enum and adjust severity. The ethereum best practices guide says that smaller datatypes like int8’s are more vulnerable than int256’s. But on the other hand, if we can do some static analysis and determine this is boilerplate code, that might change things drastically. Dunno yet.

Of course, the false positive should get tracked down.

[JoranHonig]

@chronaeon I’m not sure about that. The different false positives might be caused by different aspects in mythril. So we’d need to validate/triage them first to see if they are the same false positive. If two false positives have the same root cause, I’m fine with merging them