The test case avoids a Stack Overflow by fixing a bad loop exit condition (and start index).

The test case shows a Stack Overflow with a bad loop exit condition (and start index).

The test case avoids a Stack Overflow by fixing a bad array index.

The test case shows a Stack Overflow with an off-by-one array index.

The test case avoids a Stack Overflow by fixing a bad array index.

The test case shows a Stack Overflow with a bad array index.

The test case avoids a resource injection weakness in a scoping context.

The test case shows a resource injection weakness in a scoping context.

The test case avoids a resource injection with a string which is in a structure.

The test case shows a resource injection with a string which is in a structure.

The test case avoids a resource injection.

The test case shows a resource injection.

The test case avoids a resource injection with an address alias level code complexity.

The test case shows a resource injection with an address alias level code complexity.

The test case avoids an OS Command Injection in scope complexity.

The test case exposes an OS Command Injection in scope complexity.

The test case avoids an OS Command Injection weakness in a loop.

The test case exposes an OS Command Injection weakness in a loop.

The test case avoids an OS Command Injection weakness in a local control flow.

The test case exposes an OS Command Injection weakness in a local control flow.

The test case avoids a null dereference.

The test case exposes a null dereference.

The test case avoids a null dereference with an address alias level as code complexity.

The test case exposes a null dereference with an address alias level as code complexity.

The test case avoids a buffer overflow by using an appropriate function when argv contains tainted data.