Page History

Anchor
abnormal termination abnormal termination

abnormal termination [Open Group 08]
Abnormal termination occurs when requested by the abort() function or when some signals are received. See also #normal termination.

Anchor
asynchronous-safe asynchronous-safe

asynchronous-safe [GNU Pth]
A function is asynchronous-safe, or asynchronous-signal safe, if it can be called safely and without side effects from within a signal handler context. That is, it must be able to be interrupted at any point and run linearly out of sequence without causing an inconsistent state. It must also function properly when global data might itself be in an inconsistent state. Some asynchronous-safe operations are listed here:

• call the signal() function to reinstall a signal handler
• unconditionally modify a volatile sig_atomic_t variable (as modification to this type is atomic)
• call the _Exit() function to immediately terminate program execution
• invoke an asynchronous-safe function, as specified by your implementation

Few functions are asynchronous-safe. If a function performs any other operations, it is probably not asynchronous-safe.

Anchor
availability availability

availability [IEEE Std 610.12 1990]
The degree to which a system or component is operational and accessible when required for use. Often expressed as a probability.

Anchor
basic exception safety basic exception safety

basic exception safety [Stroustrup 01], [Sutter 00]
The basic exception safety guarantee is a property of an operation such that, if the operation terminates by raising an exception, it preserves program state invariants and prevents resource leaks. See also: exception safety, strong exception safety, no-throw guarantee.

Anchor
conforming program conforming program

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

Anchor
data race data race

data race [ISO/IEC Document Number N3000 – Working Draft, Standard for Programming Language C++, November 2009]
The execution of a program contains a data race if it contains two conflicting actions in different threads, at least one of which is not atomic, and neither happens before the other. Any such data race results in undefined behavior.

Anchor
deadlock deadlock

deadlock
A condition where one or more threads is unable to continue execution because it is blocked waiting for some thread (including itself) to satisfy some condition.

Anchor
denial-of-service denial-of-service

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

Anchor
error tolerance error tolerance

error tolerance [IEEE Std 610.12 1990]
The ability of a system or component to continue normal operation despite the presence of erroneous inputs.

Anchor
exception safety exception safety

exception safety [Stroustrup 01]
An operation on an object is said to be exception safe if that operation leaves the object in a valid state when the operation is terminated by throwing an exception. See also: basic exception safety, strong exception safety, no-throw guarantee.

Anchor
exploit exploit

exploit [Seacord 05a]
An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit security policy.

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 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 example, a traffic light that continues to alternate between red and green if the yellow light fails.

Anchor
fault tolerance fault tolerance

fault tolerance [IEEE Std 610.12 1990]
The ability of a system or component to continue normal operation despite the presence of hardware or software faults.

Anchor
free store free store

free store [ISO/IEC 14882-2003]
Storage managed by the C++ allocation and deallocation functions ::operator new(std::size_t), ::operator delete(void*), their array forms ::operator new[](std::size_t), ::operator delete[](void*), overloads of said functions on std::nothrow_t, any user-defined replacements for said functions, as well as any such functions defined as a member of a class. Storage in the free store is distinct from storage managed by the C functions calloc, free, malloc, and realloc.

Anchor
freestanding environment freestanding environment

Anchor
freestanding implementation freestanding implementation

freestanding implementation [ISO/IEC 14882-2003]
A freestanding implementation is one in which execution may take place without the benefit of an operating system, and has an implementation-defined set of libraries that includes certain language-support libraries. Also referred to as freestanding environment.

Anchor
function-like macro function-like macro

function-like macro [ISO/IEC 9899-1999]
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

Anchor
hosted implementation hosted implementation

hosted implementation [ISO/IEC 14882-2003]
An implementation that is not freestanding. Program startup occurs at main(), complex types are implemented, and all C++ standard library facilities are available. Also referred to as hosted environment.

Anchor
ill-formed ill-formed

Anchor
ill-formed program ill-formed program

ill-formed program [ISO/IEC 14882-2003]
A C++ program that is not #well-formed, that is a program not constructed according to the syntax rules, diagnosable semantic rules, and the #One Definition Rule.

Anchor
implementation implementation

implementation [ISO/IEC 9899-1999]
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 14882-2003]
Behavior, for a #well-formed program construct and correct data, that depends on the implementation and that each implementation shall document.

Anchor
incomplete type incomplete type

incomplete type [ISO/IEC 14882-2003]
A type that describes objects but lacks information needed to determine their sizes.

Anchor
indeterminate value indeterminate value

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

Anchor
invalid pointer invalid pointer

invalid pointer
A pointer that is not a #valid pointer.

Anchor
locale-specific behavior locale-specific behavior

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

Anchor
lvalue lvalue

lvalue [ISO/IEC 9899-1999]
An lvalue is 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 05a]
Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities.

Anchor
normal termination normal termination

normal termination [Open Group 08]
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
no-throw guarantee no-throw guarantee

no-throw guarantee [Sutter 00]
The no-throw guarantee is a property of an operation such that it is guaranteed to complete successfully without raising or propagating an exception. See also: exception safety, basic exception safety, strong exception safety.

Anchor
object-like macro object-like macro

object-like macro [ISO/IEC 9899-1999]
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
one definition rule one definition rule

Anchor
odr odr

one definition rule (ODR) [ISO/IEC 14882-2003]
A fundamental C++ rule that states that no translation unit shall contain more than one definition of any variable, function, class type, enumeration type or template.

Anchor
reentrant reentrant

reentrant [Dowd 06]
A function is reentrant if multiple instances of the same function can run in the same address space concurrently without creating the potential for inconsistent states.

Anchor
reliability reliability

reliability [IEEE Std 610.12 1990]
The ability of a system or component to perform its required functions under stated conditions for a specified period of time.

Anchor
robustness robustness

robustness [IEEE Std 610.12 1990]
The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions.

Anchor
rvalue rvalue

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

Anchor
security flaw security flaw

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

Anchor
security policy security policy

security policy [Internet Society 00]
A set of rules and practices that specify or regulate how a system or organization provides security services to protect sensitive and critical system resources.

Anchor
sequence point sequence point

sequence point C99 [ISO/IEC 9899-1999]
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.

The following sequence points are defined by C99 [ISO/IEC 9899-1999]:

• the call to a function, after the arguments have been evaluated
• the end of the first operand of the following operators: && (logical AND); || (logical OR); ? (conditional); , (comma operator)
• the end of a full declarator
• the end of a full expression: an initializer; the expression in an expression statement (that is, at the semicolon); the controlling expression of a selection statement (if or switch); the controlling expression of a while or do statement; each of the expressions of a for statement; the expression in a return statement
• immediately before a function returns
• after the actions associated with each formatted input/output function conversion specifier
• immediately before and immediately after each call to a comparison function, by a standard searching or sorting function, and between any call to a comparison function and any movement of the objects passed as arguments to that call

Note that not all instances of a comma in C code denote a usage of the comma operator. For example, the comma between arguments in a function call is not a sequence point.

Anchor
strictly conforming strictly conforming

strictly conforming [ISO/IEC 9899-1999]
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't, for example, depend upon implementation-defined behavior.

Anchor
strong exception safety strong exception safety

strong exception safety [Stroustrup 01], [Sutter 00]
The strong exception safety guarantee is a property of an operation such that, in addition to satisfying the basic exception safety guarantee, if the operation terminates by raising an exception it has no observable effects on program state. See also: exception safety, basic exception safety, no-throw guarantee.

Anchor
trap representation trap representation

trap representation [ISO/IEC 9899-1999]
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 14882-2003]
Behavior, such as might arise upon use of an erroneous program construct or erroneous data, for which the C++ Standard imposes no requirements. Undefined behavior may also be expected when the C++ Standard omits the description of any explicit definition of behavior.

Anchor
unsafe function-like macro unsafe function-like macro

unsafe function-like macro
A #function-like macro whose expansion causes one or more of its arguments not to be evaluated exactly once.

Anchor
unspecified behavior unspecified behavior

unspecified behavior [ISO/IEC 14882-2003]
Behavior, for a #well-formed program construct and correct data, that depends on the implementation. The implementation is not required to document which behavior occurs.

Anchor
unspecified value unspecified value

unspecified value [ISO/IEC 9899-1999]
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 6.5.8p3)
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.

Anchor
validation validation

validation [IEC 61508-4]
Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.

Anchor
verification verification

verification [IEC 61508-4]
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled.

Anchor
vulnerability vulnerability

vulnerability [Seacord 05a]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.

Anchor
well-formed well-formed

Anchor
well-formed program well-formed program

well-formed program [ISO/IEC 14882-2003]
A C++ program constructed according to the syntax rules, diagnosable semantic rules, and the #One Definition Rule. See also #ill-formed program.