Skip to content

Subject: Export/declaration mismatches

A single-release audit (no old/new comparison) finds the binary's export table and its own public headers disagreeing -- an accidental export, a private header leak, an unversioned export, or a declaration with no matching export and vice versa.

9 case(s). ← back to all subjects

Cases

Case Title Verdict Category
case143_audit_accidental_export Accidental Export (Single-Release Audit) 🟢 COMPATIBLE Quality (Compatible)
case144_audit_private_header_leak Private Header Leak (Single-Release Audit) 🟢 COMPATIBLE Quality (Compatible)
case146_audit_rtti_for_internal RTTI Exported for an Internal Type (Single-Release Audit) 🟢 COMPATIBLE Quality (Compatible)
case147_scan_depth_ladder Depth Ladder — the Same Input Answered at Increasing Depth 🟢 COMPATIBLE Quality (Compatible)
case148_xcheck_header_build_mismatch Header Build-Context Mismatch (Cross-Source Flagship) 🟠 API_BREAK API Break
case149_xcheck_odr_variant ODR Type Variant (Cross-Source, L4 Layout ↔ Layout) 🟠 API_BREAK API Break
case150_xcheck_export_public_pair Bidirectional Export ↔ Declaration Pair 🟢 COMPATIBLE Quality (Compatible)
case151_xcheck_provider_matrix Provider-Agreement Matrix (Corroboration Grows With Evidence) 🟢 COMPATIBLE Quality (Compatible)
case181_xcheck_public_to_internal_dependency Public API Reaches an Internal Declaration 🟢 COMPATIBLE Quality (Compatible)