Page History

...

Anchor
async-signal-safe async-signal-safe

async-signal-safe function [ISO/IEC 9945:2008]
A function that may be invoked, without restriction, from signal-catching functions. No function [(defined in ISO/IEC 9945] ) is async-signal-safe unless explicitly described as such. See also asynchronous-safe.

...

Anchor
conforming program conforming program

conforming [ISO/IEC 9899-19992011]
Conforming programs may depend on nonportable features of a conforming implementation.

...

Anchor
denial-of-service denial-of-service

Anchor
dos dos

denial-of-service attack
Also DoS attack. An attempt to make a computer resource unavailable to its intended users.

...

Anchor
fail safe fail safe

fail safe [IEEE Std 610.12 1990]
Pertaining to a system or component that automatically places itself in a safe operating mode in the event of a failure; for failure—for example, a traffic light that reverts to blinking red in all directions when normal operation fails.

Anchor
fail soft fail soft

fail soft [IEEE Std 610.12 1990]
Pertaining to a system or component that continues to provide partial operational capability in the event of certain failures; for failures—for example, a traffic light that continues to alternate between red and green if the yellow light fails.

...

Anchor
freestanding environment freestanding environment

freestanding environment [ISO/IEC 9899-19992011]
An environment in which C program execution may take place without any benefit of an operating system.   Program startup might occur at some function other than main(), complex types might not be implemented, and only certain minimal library facilities are guaranteed to be available.

Anchor
function-like macro function-like macro

function-like macro [ISO/IEC 9899-19992011]
A #define preprocessing directive that defines an identifier immediately followed by zero or more parameters, the ellipsis (...), or a combination of the two, enclosed in parentheses, similar syntactically to a function call. Subsequent instances of the macro name followed by a parenthesized list of arguments in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also object-like macro and unsafe function-like macro.

Anchor
hosted environment hosted environment

hosted environment [ISO/IEC 9899-19992011]
An environment that is not freestanding.   Program startup occurs at main(), complex types are implemented, and all C standard Standard library facilities are available.

Anchor
implementation implementation

implementation [ISO/IEC 9899-19992011]
Particular set of software, running in a particular translation environment under particular control options, that performs translation of programs for, and supports execution of functions in, a particular execution environment.

Anchor
implementation-defined behavior implementation-defined behavior

implementation-defined behavior [ISO/IEC 9899-19992011]
Unspecified behavior whereby each implementation documents how the choice is made.

Anchor
incomplete type incomplete type

incomplete type [ISO/IEC 9899-19992011]
A type that describes an identifier but lacks information needed to determine the size of the identifier.

Anchor
indeterminate value indeterminate value

indeterminate value [ISO/IEC 9899-19992011]
Either an unspecified value or a trap representation.

...

Anchor
locale-specific behavior locale-specific behavior

locale-specific behavior [ISO/IEC 9899-19992011]
Behavior that depends on local conventions of nationality, culture, and language that each implementation documents.

Anchor
lvalue lvalue

lvalue [ISO/IEC 9899-19992011]
An expression with an object type or an incomplete type other than void. The name lvalue comes originally from the assignment expression E1 = E2, in which the left operand E1 is required to be a (modifiable) lvalue. It is perhaps better considered as representing an object "locator value.".

Anchor
mitigation mitigation

mitigation [Seacord 2005a]
Methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities.

Anchor
normal termination normal termination

normal termination [Open Group 2008]
Normal termination occurs by a return from main(), when requested with the exit(), _exit(), or _Exit() functions; , or when the last thread in the process terminates by returning from its start function, by calling the pthread_exit() function, or through cancellation. See also abnormal termination.

Anchor
object-like macro object-like macro

object-like macro [ISO/IEC 9899-19992011]
A #define preprocessing directive that defines an identifier with no parentheses. Subsequent instances of the macro name in a translation unit are replaced by the replacement list of preprocessing tokens that constitute the remainder of the directive. See also function-like macro.

...

Anchor
rvalue rvalue

rvalue [ISO/IEC 9899-19992011]
Value of an expression.

Anchor
security flaw security flaw

security flaw [Seacord 2005a]
A software defect that poses a potential security risk.

...

Anchor
sequence point sequence point

sequence point C99 [ISO/IEC 9899-19992011]
Evaluation of an expression may produce side effects. At specific points in the execution sequence called sequence points, all side effects of previous evaluations have completed, and no side effects of subsequent evaluations have yet taken place.

Anchor
side effect side effect

Anchor
side effects side effects

side effect [ISO/IEC 9899-19992011]
Changes in the state of the execution environment achieved by accessing a volatile object, modifying an object, modifying a file, or calling a function that does any of those operations.
Note: The IEC 60559 standard for binary floating-point arithmetic requires certain user-accessible status flags and control modes. Floating-point operations implicitly set the status flags; modes affect result values of floating-point operations. Implementations that support such floating-point state are required to regard changes to it as side effects. These are detailed in Annex F of the C Standard.

Anchor
strictly conforming strictly conforming

strictly conforming [ISO/IEC 9899-19992011]
A strictly conforming program is one that uses only those features of the language and library specified in the international standard. Strictly conforming programs are intended to be maximally portable among conforming implementations and can'tcannot, for example, depend on implementation-defined behavior.

Anchor
trap representation trap representation

trap representation [ISO/IEC 9899-19992011]
Object representation that does not represent a value of the object type. Attempting to read the value of an object that has a trap representation other than by an expression that has a character type is undefined. Producing such a representation by a side effect that modifies all or any part of the object other than by an expression that has a character type is undefined.

Anchor
undefined behavior undefined behavior

undefined behavior [ISO/IEC 9899-19992011]
Behavior, upon use of a nonportable or erroneous program construct or of erroneous data, for which the standard imposes no requirements. An example of undefined behavior is the behavior on integer overflow.

...

Anchor
unspecified behavior unspecified behavior

unspecified behavior [ISO/IEC 9899-19992011]
Behavior for which the standard provides two or more possibilities and imposes no further requirements on which is chosen in any instance.

Anchor
unspecified value unspecified value

unspecified value [ISO/IEC 9899-19992011]
A valid value of the relevant type where the C Standard imposes no requirements on which value is chosen in any instance. An unspecified value cannot be a trap representation.

Anchor
valid pointer valid pointer

valid pointer
A pointer that refers to an element within an array or one past the last element of an array. For the purposes of this definition, a pointer to an object that is not an element of an array behaves the same as a pointer to the first element of an array of length one with the type of the object as its element type . (Cf. C Standard, section 6.5.8p3)
8, paragraph 3 [ISO/IEC 9899-2011]). For the purposes of this definition, an object can be considered to be an array of a certain number of bytes; that number is the size of the object, as produced by the sizeof operator.

...