| Anchor | ||||
|---|---|---|---|---|
|
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 | ||||
|---|---|---|---|---|
|
application binary interface
An interface application binary interface is an interface between two independently compiled modules of a program. An Application Binary Interface document specifies a set of conventions such as the order and location of function arguments that compilers must adhere to in order to achieve interoperability between such modules.
| Anchor | asynchronous-safe | asynchronous-safe |
|---|
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_tvariable (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.
...
|
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 and strong exception safety.)
| Anchor | ||||
|---|---|---|---|---|
|
Clang
Clang is an open source C and C++ compiler. More information can be found at http://clang.llvm.org/.
| Anchor | ||||
|---|---|---|---|---|
|
condition predicate
A condition predicate is an expression constructed from the variables of a function that must be true for a thread to be allowed to continue execution.
| Anchor | ||||
|---|---|---|---|---|
|
conforming [ISO/IEC 14882-2014]
Conforming programs may depend on nonportable features of a conforming implementation.
| Anchor | ||||
|---|---|---|---|---|
|
critical sections
Critical sections are code that accesses shared data and that would otherwise be protected from data races.
| Anchor | ||||
|---|---|---|---|---|
|
cv-qualify
To cv-qualify a type is to add
const or volatile (or both) to the type.| Anchor | ||||
|---|---|---|---|---|
|
data race [ISO/IEC 14882-2014]
The execution of a program contains a data race if it contains two potentially concurrent conflicting actions, at least one of which is not atomic, and neither happens before the other. [An exception is]that two accesses to the same object of type
volatile sig_atomic_t do not result in a data race if both occur in the same thread, even if one or more occurs in a signal handler.| Anchor | ||||
|---|---|---|---|---|
|
deadlock [ISO/IEC 14882-2014]
A deadlock is when one or more threads are unable to continue execution because each is blocked waiting for one or more of the others to satisfy some condition
| Anchor | ||||
|---|---|---|---|---|
|
denial-of-service attack
A denial-of-service attack is an attempt to make a computer resource unavailable to its intended users.
Anchor diagnostic message diagnostic message
diagnostic message [ISO/IEC 14882-2014]
A diagnostic message is a message belonging to an implementation-defined subset of the implementation’s message output. A diagnostic message may indicate a constraint violation or a valid, but questionable, language construct. Messages typically include the file name and line number pointing to the offending code construct. In addition, implementations also often indicate the severity of the problem. Although the C++ Standard does not specify any such requirement, the most severe problems often cause implementations to fail to fully translate a translation unit. Diagnostics output in such cases are termed errors. Other problems may cause implementations simply to issue a warning message and continue translating the rest of the program. (See error message and warning message.)
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
error message
An error message is a diagnostic message generated when source code is encountered that prevents an implementation from translating a translation unit. (See diagnostic message and warning message.)
| Anchor | ||||
|---|---|---|---|---|
|
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 and strong exception safety.)
| Anchor | ||||
|---|---|---|---|---|
|
exploit [Seacord 2005]
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 | ||||
|---|---|---|---|---|
|
fatal diagnostic
A fatal diagnostic is a message that causes an implementation not to perform the translation.
| Anchor | ||||
|---|---|---|---|---|
|
free store [ISO/IEC 14882-2014]
The free store is 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 | ||||
|---|---|---|---|---|
|
GCC
GCC is an open source C and C++ compiler. More information can be found at https://gcc.gnu.org/
...
critical sections
Code that accesses shared data, and that would otherwise be protected from data races.
Anchor
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.
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.
An attempt to make a computer resource unavailable to its intended users.
A diagnostic message is a message belonging to an implementation-defined subset of the implementation’s message output. A diagnostic message may indicate a constraint violation or a valid but questionable language construct. Messages typically include the file name and line number pointing to the offending code construct. In addition, implementations also often indicate the severity of the problem. Although the C++ Standard does not specify any such requirement, the most severe problems often cause implementations to fail to fully translate a translation unit. Diagnostics output in such cases are termed errors. Other problems may cause implementations simply to issue a warning message and continue translating the rest of the program. See error message and warning message.
A diagnostic message generated when source code is encountered that prevents an implementation from translating a translation unit. See diagnostic message and warning message.
The ability of a system or component to continue normal operation despite the presence of erroneous inputs.
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, and no-throw guarantee.
An exploit is a piece of software or technique that takes advantage of a security vulnerability to violate an explicit or implicit security policy.
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.
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.
A diagnostic message which causes an implementation not to perform the translation.
The ability of a system or component to continue normal operation despite the presence of hardware or software faults.
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.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.
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.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 | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
ill-formed program [ISO/IEC 14882-20032014]
A C An ill-formed program is 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 [ISO/IEC 9899-1999:2011]
Particular An implementation is a 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 [ISO/IEC 14882-2003]
Behavior2014]
Implementation-defined behavior is behavior, for a well-formed program construct and correct data, that depends on the implementation and that each implementation shall documentdocuments.
| Anchor | ||||
|---|---|---|---|---|
|
incomplete type [ISO/IEC 14882-20032014]
A type that describes objects but lacks information needed to determine their sizesclass that has been declared but not defined, an enumeration type in certain contexts, an array of unknown size or of incomplete element type, and the
void type are incomplete types. These types lack the information required to determine the size of the type.| Anchor | ||||
|---|---|---|---|---|
|
indeterminate value [ISO/IEC 989914882-1999]
Either an unspecified value or a trap representation2014]
When storage for an object with automatic or dynamic storage duration is obtained, the object has an indeterminate value, and if no initialization is performed for the object, that object retains an indeterminate value until that value is replaced.
| Anchor | ||||
|---|---|---|---|---|
|
invalid pointer
A pointer An invalid pointer is a pointer that is not a valid pointer.
| Anchor | locale-specific behavior | locale-specific behavior |
|---|
Behavior that depends on local conventions of nationality, culture, and language that each implementation documents.
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."Mitigations are methods, techniques, processes, tools, or runtime libraries that can prevent or limit exploits against vulnerabilities.
|
libc++
libc++ is an open source Standard Template Library (STL) implementation. More information can be found at http://libcxx.llvm.org/.
| Anchor | ||||
|---|---|---|---|---|
|
libstdc++
libstdc++ is an open source Standard Template Library (STL) implementation. More information can be found at https://gcc.gnu.org/onlinedocs/libstdc++/.
| Anchor | ||||
|---|---|---|---|---|
|
liveness
Liveness is when every operation or method invocation executes to completion without interruptions, even if it goes against safety.
| Anchor | ||||
|---|---|---|---|---|
|
lvalue [ISO/IEC 14882-2014]
An lvalue (so called, historically, because lvalues could appear on the left-hand side of an assignment expression) designates a function or an object.
| Anchor | ||||
|---|---|---|---|---|
|
Microsoft Visual Studio
Microsoft Visual Studio is a commercial C and C++ compiler. More information can be found at https://www.visualstudio.com/.
| Anchor | ||||
|---|---|---|---|---|
|
Microsoft Visual Studio STL
The Microsoft Visual Studio STL is a commercial Standard Template Library (STL) implementation. More information can be found at https://msdn.microsoft.com/en-us/library/cscc687y.aspx
| Anchor | ||||
|---|---|---|---|---|
|
mitigation [Seacord 2005]
A mitigation is a method, technique, process, tool, or runtime library that can prevent or limit exploits against vulnerabilities
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.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, and strong exception safety.
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 | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
one-definition rule (ODR) [ISO/IEC 14882-2014]
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, and that every program shall contain exactly one definition of every non-inline function or variable. Some definitions may be duplicated in multiple translation units, subject to strict rules.
Anchor
|
ODR-use [ISO/IEC 14882-2014
A function or object is reentrant if multiple instances of the same function can run in the same address space concurrently without creating the potential for inconsistent statesODR-used if the address of the entity is taken, the function is called, or a reference is bound to the object. When a function or object is ODR-used, its definition must exist within the program or else the program is ill-formed.
reliabilityAnchor RAII
The ability of a system or component to perform its required functions under stated conditions for a specified period of time.
The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions.
Value of an expression.
A security flaw is a software defect that poses a potential security risk.
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.
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.
RAII
RAII (Resource Acquisition Is Initialization)
RAII is a design principle supported by C++. Holding a resource is a class invariant where the allocation of the resource (acquisition) is inseparable from the initialization of the object during its construction. Further, deallocation of the resource is performed during the destruction of the object. Thus, the resource is held when initialization completes and remains held until finalization begins, ensuring there are no resource leaks unless the object owning the resource is also leaked.
| Anchor | ||||
|---|---|---|---|---|
|
reliability [IEEE Std 610.12 1990]
Reliability is the ability of a system or component to perform its required functions under stated conditions for a specified period of time.
| Anchor | ||||
|---|---|---|---|---|
|
restricted sink [ISO/IEC 9899:2011]
A restricted sink is an operand or argument whose domain is a subset of the domain described by its type.
| Anchor | ||||
|---|---|---|---|---|
|
rvalue [ISO/IEC 14882-2014]
An rvalue (so called, historically, because rvalues could appear on the right-hand side of an assignment expression), is an xvalue, a temporary object or subobject thereof, or a value that is not associated with an object.
| Anchor | ||||
|---|---|---|---|---|
|
security flaw [Seacord 2005]
A security flaw is a software defect that poses a potential security risk.
| Anchor | ||||
|---|---|---|---|---|
|
security policy [Internet Society 2000]
A security policy is 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 | ||||
|---|---|---|---|---|
|
strong exception safety [Stroustrup 2001, Sutter 2000]
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 and basic exception safety.)
| Anchor | ||||
|---|---|---|---|---|
|
SFINAE
SFINAE (Substitution Failure Is Not An Error) is a language rule applied by the compiler during overload resolution involving templates. In some contexts, when substituting a template type parameter fails, the specialization is discarded from the overload set instead of causing a compile error. This feature is used in template metaprogramming.
| Anchor | ||||
|---|---|---|---|---|
|
tainted source [ISO/IEC TS 17961:2012]
A tainted source is an external source of untrusted data.
| Anchor | ||||
|---|---|---|---|---|
|
tainted value [ISO/IEC TS 17961:2012]
A tainted value is a value derived from a tainted source that has not been sanitized.
| Anchor | ||||
|---|---|---|---|---|
|
trust boundary
A trust boundary is a boundary between a trusted execution context (or trusted data source) in which all sub-execution contexts (or data sources) are trusted by the system and a nontrusted execution context (or nontrusted data sink)
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.
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, and no-throw guarantee.
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 [ISO/IEC 14882-20032014]
Behavior Undefined behavior is 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, or defines the behavior to be ill-formed, with no diagnostic required.
A function-like macro whose expansion causes one or more of its arguments not to be evaluated exactly once++ Standard omits the description of any explicit definition of behavior or defines the behavior to be ill-formed, with no diagnostic required.
| Anchor | ||||
|---|---|---|---|---|
|
unspecified behavior [ISO/IEC 14882-20032014]
Behavior Unspecified behavior is 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 [ISO/IEC 9899-1999:2011]
A valid An unspecified value is 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
A valid pointer is 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.Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled.
| Anchor | |||
|---|---|---|---|
|
Confirmation by examination and provision of objective evidence that the requirements have been fulfilled
|
vtable
A vtable is a common implementation technique to support dynamic method dispatch, where a class object instance includes a hidden data member that is a pointer to an array of function pointers used to resolve virtual function calls at runtime.
| Anchor | ||||
|---|---|---|---|---|
|
vulnerability [Seacord 05a]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.
A diagnostic message generated when source code is encountered that does not prevent an implementation from translating a translation unit. See diagnostic message and error message.2005]
A vulnerability is a set of conditions that allows an attacker to violate an explicit or implicit security policy.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
warning message
A warning message is a diagnostic message generated when source code is encountered that does not prevent an implementation from translating a translation unit. (See diagnostic message and error message.)
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
well-formed program [ISO/IEC 14882-2014]
A well-formed program is a C++ program constructed according to the syntax rules, diagnosable semantic rules, and the one-definition rule. (See also ill-formed program.)
| Anchor | ||||
|---|---|---|---|---|
|
xvalue
A C++ program constructed according to the syntax rules, diagnosable semantic rules, and the one-definition rule. See also ill-formed program.
2014]
An xvalue (an "eXpiring" value) also refers to an object, usually near the end of its lifetime (so that its resources may be moved, for example). An xvalue is the result of certain kinds of expressions involving rvalue references.