Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Until the early 1980s, large software development projects had a continual problem with the inclusion of headers. One group might have produced a graphics.h, for example, which started by including io.h. Another group might have produced keyboard.h, which also included io.h. If io.h cannot could not safely be included several times, arguments would break out about which header should include it. Sometimes an agreement was reached that each header should include no other headers, and as a result, some application programs started with dozens of #include lines, and sometimes they got the ordering wrong or forgot a required header.

Compliant Solution

All these complications disappeared with the discovery of a simple technique: each header should #define a symbol that means "I have already been included." The entire header is then enclosed in an inclusion include guard:

Code Block
bgColor#ccccFF
langc

#ifndef HEADER_H
#define HEADER_H

/* ... contentsContents of <header.h> ... */

#endif /* HEADER_H */

Consequently, the first time that header.h is #include'd, all of its contents are included. If the header file is subsequently #include'd again, its contents are bypassed.

Because solutions such as this one make it possible to create a header file that can be included more than once, the C standard [ISO/IEC 9899:1999] Standard guarantees that the standard headers are safe for multiple inclusion.

Note that it is a common mistake to choose a reserved name (such as _HEADER_H_ or __HEADER_H__) for the name of the macro used in the inclusion include guard. See rule DCL37-C. Do not declare or define a reserved identifier for more information.

Risk Assessment

Failure to include header files in an inclusion include guard can result in unexpected behavior.

Recommendation

Severity

Likelihood

Remediation Cost

Priority

Level

PRE06-C

low

Low

unlikely

Unlikely

low

Low

P3

L3

Automated Detection

ToolVersionCheckerDescription
section
Astrée
Include Page
Astrée_V
Astrée_V

include-guard-missing
include-guard-pragma-once

Fully checked
Axivion Bauhaus Suite

Include Page
Axivion Bauhaus Suite_V
Axivion Bauhaus Suite_V

CertC-PRE06

ECLAIR

Include Page
ECLAIR_V
ECLAIR_V

CC2.PRE06

Fully implemented
Helix QAC

Include Page
Helix QAC_V
Helix QAC_V

C0883
Klocwork
Include Page
Klocwork_V
Klocwork_V
MISRA.INCGUARD
LDRA tool suite
Include Page
LDRA_V
LDRA_V
section

243 S

Section

Fully Implemented

Section

ECLAIR

Include PageECLAIR_VECLAIR_V
Section

inclgard

SectionFully Implemented

Fully implemented
Parasoft C/C++test
Include Page
Parasoft_V
Parasoft_V

CERT_C-PRE06-a

Use multiple include guards

PC-lint Plus

Include Page
PC-lint Plus_V
PC-lint Plus_V

967

Fully supported

Polyspace Bug Finder

Include Page
Polyspace Bug Finder_V
Polyspace Bug Finder_V

CERT C: Rec. PRE06-CChecks for content of header file not guarded from multiple inclusions (rec. fully covered)


RuleChecker
Include Page
RuleChecker_V
RuleChecker_V

include-guard-missing
include-guard-pragma-once

Fully checked

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

Related Guidelines

...

...

...

ISO/IEC 9899:1999 Section 6.10, "Preprocessing directives," Section 5.1.1, "Translation environment," and Section 7.1.2, "Standard headers"

...

MISRA C:2012Directive 4.10 (required)

Bibliography

[Plum 1985]Rule 1-14


...

Image Removed      01. Preprocessor (PRE)      Image Added Image Added Image Modified