# Analysis results for test-filename.sol

## Exception State
- SWC ID: 110
- Severity: Low
- Contract: Unknown
- Function name: `assert3(uint256)`
- PC address: 446
- Estimated Gas Usage: 206 - 301

### Description

A reachable exception has been detected.
It is possible to trigger an exception (opcode 0xfe). Exceptions can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. Note that explicit `assert()` should only be used to check invariants. Use `require()` for regular input checking.

## Exception State
- SWC ID: 110
- Severity: Low
- Contract: Unknown
- Function name: `arrayaccess(uint256)`
- PC address: 484
- Estimated Gas Usage: 256 - 351

### Description

A reachable exception has been detected.
It is possible to trigger an exception (opcode 0xfe). Exceptions can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. Note that explicit `assert()` should only be used to check invariants. Use `require()` for regular input checking.

## Exception State
- SWC ID: 110
- Severity: Low
- Contract: Unknown
- Function name: `divisionby0(uint256)`
- PC address: 506
- Estimated Gas Usage: 272 - 367

### Description

A reachable exception has been detected.
It is possible to trigger an exception (opcode 0xfe). Exceptions can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. Note that explicit `assert()` should only be used to check invariants. Use `require()` for regular input checking.

## Exception State
- SWC ID: 110
- Severity: Low
- Contract: Unknown
- Function name: `assert1()`
- PC address: 531
- Estimated Gas Usage: 268 - 363

### Description

A reachable exception has been detected.
It is possible to trigger an exception (opcode 0xfe). Exceptions can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. Note that explicit `assert()` should only be used to check invariants. Use `require()` for regular input checking.