# Analysis results for /inputs/exceptions.sol ## Exception state - Type: Informational - Contract: Unknown - Function name: `_function_0x546455b5` - PC address: 446 ### Description 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 */inputs/exceptions.sol:16* ``` assert(input != 23) ``` ## Exception state - Type: Informational - Contract: Unknown - Function name: `_function_0x92dd38ea` - PC address: 484 ### Description 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 */inputs/exceptions.sol:34* ``` myarray[index] ``` ## Exception state - Type: Informational - Contract: Unknown - Function name: `_function_0xa08299f1` - PC address: 506 ### Description 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 */inputs/exceptions.sol:24* ``` 1/input ``` ## Exception state - Type: Informational - Contract: Unknown - Function name: `_function_0xb34c3610` - PC address: 531 ### Description 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 */inputs/exceptions.sol:7* ``` assert(i == 0) ```