Page History

...

CERT C Secure Coding Standard	API04-C. Provide a consistent and usable error-checking mechanism ERR00-C. Adopt and implement a consistent and comprehensive error-handling policy ERR02-C. Avoid in-band error indicators ERR05-C. Application-independent code should provide error detection without dictating error handling EXP12-C. Do not ignore values returned by functions EXP34-C. Do not dereference null pointers FIO10-C. Take care when using the rename() function FIO13-C. Never push back anything other than one read character FIO33-C. Detect and handle input output errors resulting in undefined behaviorvoid FIO35 FIO34-C. Use feof() and ferror() to detect end-of-file and file errors when sizeof(int) == sizeof(char)Distinguish between characters read from a file and EOF or WEOF FLP03-C. Detect and handle floating-point errors FLP32-C. Prevent or detect domain and range errors in math functions MEM04-C. Do not perform zero-length allocations MEM12-C. Consider using a goto chain when leaving a function on error when using and releasing resources
CERT C++ Secure Coding Standard	ERR10-CPP. Check for error conditions FIO04-CPP. Detect and handle input and output errors
ISO/IEC TS 17961	Failing to detect and handle standard library errors [liberr]
MITRE CWE	CWE-252, Unchecked return value CWE-253, Incorrect check of function return value CWE-390, Detection of error condition without action CWE-391, Unchecked error condition

...

Space shortcuts