check

Syntax

Linux OS and OS X:

-check=keyword[, keyword...]

Windows OS:

/check:keyword[, keyword...]

Arguments

keyword

Specifies the conditions to check. Possible values are:

[no]conversions	Determines whether checking occurs for converting to smaller types. Keyword conversions enables this checking.
[no]stack	Determines whether checking occurs on the stack frame. Keyword stack enables this checking. If stack is specified, the stack is checked for buffer overruns and buffer underruns. This option also enforces local variables initialization and stack pointer verification.
[no]uninit	Determines whether checking occurs for uninitialized variables. Keyword uninit enables this checking. If a variable is read before it is written, a run-time error routine will be called.

Default

noconversions
nostack
nouninit

No checking is performed for the above run-time conditions.

Description

This option checks for certain conditions at run time.

On Windows* OS, this option disables any default or specified optimizations and applies the /Od level of optimization. If you specified optimizations, the compiler emits warning diagnostics for the disabled optimizations.

On Linux* OS and OS X*, this option may disable some optimizations.

Note

This option requires library support. Depending on the platform, the required library is either in your operating system run-time environment or in your compiler package.

IDE Equivalent

Windows: None

Linux: Runtime > Check Stack Frame (-check=stack)

Runtime > Check Type Conversions (-check=conversions)

Runtime > Check Uninitialized Variables (-check=uninit)

OS X: Runtime > Check Stack Frame (-check=stack)

Runtime > Check Type Conversions (-check=conversions)

Runtime > Check Uninitialized Variables (-check=uninit)

Alternate Options

check conversions

Linux and OS X: None

Windows: /RTCc

check stack

Linux and OS X: None

Windows: /RTCs

check uninit

Linux and OS X: None

Windows: /RTCu