Space Tools

An 'undefined' page is any page that has been linked to from within Confluence, but that does not yet exist.

1. Prev
2. 1
3. 2
4. 3
5. 4
6. 5
7. 6
8. 7
9. Next

Undefined Page	Linked From
CON32-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed	Comment: CON34-C. Declare objects shared between threads with appropriate storage durations > Re: CON34-C. Declare objects shared between threads with appropriate storage durations (SEI CERT C Coding Standard) Comment: POS38-C. Beware of race conditions when using fork and file descriptors > Re: POS38-C. Beware of race conditions when using fork and file descriptors (SEI CERT C Coding Standard)
DCL30-C. Declare objects with appropriate storage durations	Page: Draft Agenda and Minutes January 5, 2011 (CSCG) Page: Draft Minutes January 5, 2011 (CSCG) Page: Draft Agenda January 18, 2011 (CSCG) Page: Draft Minutes January 18, 2011 (CSCG)
DCL32-C. Guarantee that mutually visible identifiers are unique)	Comment: DCL02-C. Use visually distinct identifiers > Re: DCL02-C. Use visually distinct identifiers (SEI CERT C Coding Standard)
DCL34-C. Use volatile for data that cannot be cached	Comment: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction > Re: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction (SEI CERT C Coding Standard) Comment: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction > Re: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction (CInternalTest) Comment: CON43-C. Do not allow data races in multithreaded code > Re: CON43-C. Do not allow data races in multithreaded code (SEI CERT C Coding Standard)
DCL39-C. Avoid information leak in structure padding	Comment: EXP42-C. Do not compare padding data > Re: EXP42-C. Do not compare padding data (SEI CERT C Coding Standard)
ERR31-C. Don't redefine errno	Comment: DCL37-C. Do not declare or define a reserved identifier > Re: DCL37-C. Do not declare or define a reserved identifier (SEI CERT C Coding Standard)
EXP30-C. Do not depend on order of evaluation between sequence points	Comment: EXP35-C. Do not modify objects with temporary lifetime > Re: EXP35-C. Do not modify objects with temporary lifetime (SEI CERT C Coding Standard)
EXP31-C. Avoid side effects in assertions	Comment: PRE31-C. Avoid side effects in arguments to unsafe macros > Re: PRE31-C. Avoid side effects in arguments to unsafe macros (CInternalTest) Comment: PRE31-C. Avoid side effects in arguments to unsafe macros > Re: PRE31-C. Avoid side effects in arguments to unsafe macros (SEI CERT C Coding Standard)
EXP32-C. Do not access a volatile object through a non-volatile reference	Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
EXP33-C. Do not reference uninitialized memory	Comment: DCL31-C. Declare identifiers before using them > Re: DCL31-C. Declare identifiers before using them (SEI CERT C Coding Standard) Comment: DCL31-C. Declare identifiers before using them > Re: DCL31-C. Declare identifiers before using them (CInternalTest)
EXP37-C. Call functions with the arguments intended by the API	Comment: DCL05-C. Use typedefs of non-pointer types only > Re: DCL05-C. Use typedefs of non-pointer types only (SEI CERT C Coding Standard)
EXP40-C. Do not modify constant values	Comment: EXP32-C. Do not access a volatile object through a nonvolatile reference > Re: EXP32-C. Do not access a volatile object through a nonvolatile reference (CInternalTest) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP32-C. Do not access a volatile object through a nonvolatile reference > Re: EXP32-C. Do not access a volatile object through a nonvolatile reference (SEI CERT C Coding Standard)
Edited comment, had dropped some parts\	Comment: Rule 11. Signals (SIG) > Re: Rule 11. Signals (SIG) (SEI CERT C Coding Standard)
FIO00-C. Take care when creating format strings	Comment: void FIO33-C. Detect and handle input output errors resulting in undefined behavior > Re: void FIO33-C. Detect and handle input output errors resulting in undefined behavior (SEI CERT C Coding Standard)
FIO02-C. Canonicalize path names originating from untrusted sources	Comment: VOID 2010 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2010 CWE SANS Top 25 Most Dangerous Programming Errors (SEI CERT C Coding Standard)
e\	Comment: ENV03-C. Sanitize the environment when invoking external programs > Re: ENV03-C. Sanitize the environment when invoking external programs (SEI CERT C Coding Standard)
edit\	Comment: INT13-C. Use bitwise operators only on unsigned operands > Re: INT13-C. Use bitwise operators only on unsigned operands (SEI CERT C Coding Standard)
even before David's reply\	Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
CON32-C. When data must be accessed by multiple threads, provide a mutex and guarantee no adjacent data is also accessed	Comment: CON34-C. Declare objects shared between threads with appropriate storage durations > Re: CON34-C. Declare objects shared between threads with appropriate storage durations (SEI CERT C Coding Standard) Comment: POS38-C. Beware of race conditions when using fork and file descriptors > Re: POS38-C. Beware of race conditions when using fork and file descriptors (SEI CERT C Coding Standard)
DCL30-C. Declare objects with appropriate storage durations	Page: Draft Agenda and Minutes January 5, 2011 (CSCG) Page: Draft Minutes January 5, 2011 (CSCG) Page: Draft Agenda January 18, 2011 (CSCG) Page: Draft Minutes January 18, 2011 (CSCG)
DCL32-C. Guarantee that mutually visible identifiers are unique)	Comment: DCL02-C. Use visually distinct identifiers > Re: DCL02-C. Use visually distinct identifiers (SEI CERT C Coding Standard)
DCL34-C. Use volatile for data that cannot be cached	Comment: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction > Re: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction (SEI CERT C Coding Standard) Comment: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction > Re: CON01-C. Acquire and release synchronization primitives in the same module, at the same level of abstraction (CInternalTest) Comment: CON43-C. Do not allow data races in multithreaded code > Re: CON43-C. Do not allow data races in multithreaded code (SEI CERT C Coding Standard)
DCL39-C. Avoid information leak in structure padding	Comment: EXP42-C. Do not compare padding data > Re: EXP42-C. Do not compare padding data (SEI CERT C Coding Standard)
ERR31-C. Don't redefine errno	Comment: DCL37-C. Do not declare or define a reserved identifier > Re: DCL37-C. Do not declare or define a reserved identifier (SEI CERT C Coding Standard)
EXP30-C. Do not depend on order of evaluation between sequence points	Comment: EXP35-C. Do not modify objects with temporary lifetime > Re: EXP35-C. Do not modify objects with temporary lifetime (SEI CERT C Coding Standard)
EXP31-C. Avoid side effects in assertions	Comment: PRE31-C. Avoid side effects in arguments to unsafe macros > Re: PRE31-C. Avoid side effects in arguments to unsafe macros (CInternalTest) Comment: PRE31-C. Avoid side effects in arguments to unsafe macros > Re: PRE31-C. Avoid side effects in arguments to unsafe macros (SEI CERT C Coding Standard)
EXP32-C. Do not access a volatile object through a non-volatile reference	Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard)
EXP33-C. Do not reference uninitialized memory	Comment: DCL31-C. Declare identifiers before using them > Re: DCL31-C. Declare identifiers before using them (SEI CERT C Coding Standard) Comment: DCL31-C. Declare identifiers before using them > Re: DCL31-C. Declare identifiers before using them (CInternalTest)
EXP37-C. Call functions with the arguments intended by the API	Comment: DCL05-C. Use typedefs of non-pointer types only > Re: DCL05-C. Use typedefs of non-pointer types only (SEI CERT C Coding Standard)
EXP40-C. Do not modify constant values	Comment: EXP32-C. Do not access a volatile object through a nonvolatile reference > Re: EXP32-C. Do not access a volatile object through a nonvolatile reference (CInternalTest) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP05-C. Do not cast away a const qualification > Re: EXP05-C. Do not cast away a const qualification (SEI CERT C Coding Standard) Comment: EXP32-C. Do not access a volatile object through a nonvolatile reference > Re: EXP32-C. Do not access a volatile object through a nonvolatile reference (SEI CERT C Coding Standard)

1. Prev
2. 1
3. 2
4. 3
5. 4
6. 5
7. 6
8. 7
9. Next