Skip to main content
assistive.skiplink.to.breadcrumbs
assistive.skiplink.to.header.menu
assistive.skiplink.to.action.menu
assistive.skiplink.to.quick.search

13. Error Handling (ERR)

Created by Robert Seacord, last modified by David Svoboda on May 14, 2008

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Recommendations

ERR00-A. Adopt and implement a consistent and comprehensive error handling policy

ERR01-A. Use ferror() rather than errno to check for FILE stream errors

ERR02-A. Avoid in-band error indicators

ERR03-A. Use runtime-constraint handlers when calling functions defined by TR24731-1

ERR04-A. Choose an appropriate termination strategy

Rules

ERR30-C. Set errno to zero before calling a function, and use it only after the function returns a value indicating failure

ERR31-C. Don't redefine errno

ERR32-C. Do not rely on indeterminate values of errno

Risk Assessment Summary

Recommendation	Severity	Likelihood	Remediation Cost	Priority	Level
ERR00-A	medium	probable	medium	P8	L2
ERR01-A	high	likely	high	P9	L2
ERR02-A	low	unlikely	high	P1	L3
ERR03-A	low	unlikely	low	P3	L3
ERR04-A	medium	unlikely	low	P6	L2

Rule	Severity	Likelihood	Remediation Cost	Priority	Level
ERR30-C	low	unlikely	low	P3	L3
ERR31-C	low	unlikely	low	P3	L3
ERR32-C	low	unlikely	low	P3	L3

Related Rules and Recommendations

DCL09-C. Declare functions that return errno with a return type of errno_t

FIO40-C. Reset strings on fgets() or fgetws() failure

FLP03-C. Detect and handle floating-point errors

FLP32-C. Prevent or detect domain and range errors in math functions

MSC11-C. Incorporate diagnostic tests using assertions

12. Signals (SIG) ERR00-A. Adopt and implement a consistent and comprehensive error handling policy

No labels