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
INT17-C. Do not make assumptions about representation of signed integers	Page: VOID INT20-C. Use the type ptrdiff_t when storing the difference of two pointers (CInternalTest2)
INT35-C. Evaluate integer expressions in a larger size before comparing or assigning to that size	Comment: INT30-C. Ensure that unsigned integer operations do not wrap > Re: INT30-C. Ensure that unsigned integer operations do not wrap (SEI CERT C Coding Standard)
INT36-C. Do not perform bitwise and arithmetic operations on the same variable	Comment: INT14-C. Avoid performing bitwise and arithmetic operations on the same data > Re: INT14-C. Avoid performing bitwise and arithmetic operations on the same data (SEI CERT C Coding Standard)
INTBUFSIZE\	Comment: EXP08-C. Ensure pointer arithmetic is used correctly > Re: EXP08-C. Ensure pointer arithmetic is used correctly (SEI CERT C Coding Standard)
MEM12-C. Consider using a Goto-Chain when leaving a function on error when using and releasing resources	Comment: Rule 48. Miscellaneous (MSC) > Re: Rule 48. Miscellaneous (MSC) (SEI CERT C Coding Standard)
MEM31-C. Free dynamically allocated memory exactly once	Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (SEI CERT C Coding Standard) Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (SEI CERT C Coding Standard) Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (CInternalTest)
MEM32-C. Detect and handle memory allocation errors	Comment: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() > Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() (CInternalTest) Comment: MEM11-C. Do not assume infinite heap space > Re: MEM11-C. Do not assume infinite heap space (CInternalTest) Comment: MEM11-C. Do not assume infinite heap space > Re: MEM11-C. Do not assume infinite heap space (SEI CERT C Coding Standard) Comment: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() > Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() (SEI CERT C Coding Standard)
MEM35-C.+Allocate+sufficient+memory+for+an+object	Comment: void STR33-C. Size wide character strings correctly > Re: void STR33-C. Size wide character strings correctly (SEI CERT C Coding Standard)
MET04-J. When defining subclasses, explicitly call the superclass constructor first	Comment: VOID Specify a default constructor that initializes each data member to a known safe state. > Re: VOID Specify a default constructor that initializes each data member to a known safe state. (SEI CERT C Coding Standard)
MSC02-C. Avoid errors of omission	Comment: API04-C. Provide a consistent and usable error-checking mechanism > Re: API04-C. Provide a consistent and usable error-checking mechanism (SEI CERT C Coding Standard) Comment: API04-C. Provide a consistent and usable error-checking mechanism > Re: API04-C. Provide a consistent and usable error-checking mechanism (CInternalTest)
MSC06-C. Be aware of compiler optimization when dealing with sensitive data	Comment: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code > Re: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code (CInternalTest) Comment: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code > Re: MSC18-C. Be careful while handling sensitive data, such as passwords, in program code (SEI CERT C Coding Standard) Comment: MEM03-C. Clear sensitive information stored in reusable resources > Re: MEM03-C. Clear sensitive information stored in reusable resources (SEI CERT C Coding Standard)
MSC12-C. Detect and remove code that has no effect	Comment: SIG01-C. Understand implementation-specific details regarding signal handler persistence > Re: SIG01-C. Understand implementation-specific details regarding signal handler persistence (SEI CERT C Coding Standard)
MSC21-C. Use inequality to terminate a for loop	Page: VOID Beware of infinite loops (CInternalTest) Page: VOID Beware of infinite loops (SEI CERT C Coding Standard) Page: VOID Beware of infinite loops (CInternalTest2)
MSC34-C. Do not use deprecated or obsolescent functions	Comment: VOID STR35-C. Do not copy data from an unbounded source to a fixed-length array > Re: VOID STR35-C. Do not copy data from an unbounded source to a fixed-length array (SEI CERT C Coding Standard)
MSC34-C. Do not use deprecated or obsolete functions	Comment: MSC33-C. Do not pass invalid data to the asctime() function > Re: MSC33-C. Do not pass invalid data to the asctime() function (SEI CERT C Coding Standard)
Open Group 04	Comment: void SIG33-C. Do not recursively invoke the raise() function > Re: void SIG33-C. Do not recursively invoke the raise() function (SEI CERT C Coding Standard)
Open Group 04\	Comment: void SIG33-C. Do not recursively invoke the raise() function > Re: void SIG33-C. Do not recursively invoke the raise() function (SEI CERT C Coding Standard)
intro.multithread\	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)
n\	Comment: ENV30-C. Do not modify the object referenced by the return value of certain functions > Re: ENV30-C. Do not modify the object referenced by the return value of certain functions (SEI CERT C Coding Standard)
nelements\	Comment: Rule 08. Memory Management (MEM) > Re: Rule 08. Memory Management (MEM) (SEI CERT C Coding Standard)
INT17-C. Do not make assumptions about representation of signed integers	Page: VOID INT20-C. Use the type ptrdiff_t when storing the difference of two pointers (CInternalTest2)
INT35-C. Evaluate integer expressions in a larger size before comparing or assigning to that size	Comment: INT30-C. Ensure that unsigned integer operations do not wrap > Re: INT30-C. Ensure that unsigned integer operations do not wrap (SEI CERT C Coding Standard)
INT36-C. Do not perform bitwise and arithmetic operations on the same variable	Comment: INT14-C. Avoid performing bitwise and arithmetic operations on the same data > Re: INT14-C. Avoid performing bitwise and arithmetic operations on the same data (SEI CERT C Coding Standard)
INTBUFSIZE\	Comment: EXP08-C. Ensure pointer arithmetic is used correctly > Re: EXP08-C. Ensure pointer arithmetic is used correctly (SEI CERT C Coding Standard)
MEM12-C. Consider using a Goto-Chain when leaving a function on error when using and releasing resources	Comment: Rule 48. Miscellaneous (MSC) > Re: Rule 48. Miscellaneous (MSC) (SEI CERT C Coding Standard)
MEM31-C. Free dynamically allocated memory exactly once	Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (SEI CERT C Coding Standard) Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (SEI CERT C Coding Standard) Comment: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors > Re: VOID 2009 CWE SANS Top 25 Most Dangerous Programming Errors (CInternalTest)
MEM32-C. Detect and handle memory allocation errors	Comment: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() > Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() (CInternalTest) Comment: MEM11-C. Do not assume infinite heap space > Re: MEM11-C. Do not assume infinite heap space (CInternalTest) Comment: MEM11-C. Do not assume infinite heap space > Re: MEM11-C. Do not assume infinite heap space (SEI CERT C Coding Standard) Comment: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() > Re: VOID Ensure that a mutex is locked successfully before calling pthread_cond_wait() (SEI CERT C Coding Standard)
MEM35-C.+Allocate+sufficient+memory+for+an+object	Comment: void STR33-C. Size wide character strings correctly > Re: void STR33-C. Size wide character strings correctly (SEI CERT C Coding Standard)
MET04-J. When defining subclasses, explicitly call the superclass constructor first	Comment: VOID Specify a default constructor that initializes each data member to a known safe state. > Re: VOID Specify a default constructor that initializes each data member to a known safe state. (SEI CERT C Coding Standard)
MSC02-C. Avoid errors of omission	Comment: API04-C. Provide a consistent and usable error-checking mechanism > Re: API04-C. Provide a consistent and usable error-checking mechanism (SEI CERT C Coding Standard) Comment: API04-C. Provide a consistent and usable error-checking mechanism > Re: API04-C. Provide a consistent and usable error-checking mechanism (CInternalTest)

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