Pointer or count exceeds its valid extent

Rule ID: correctness.pointer-count-initialization@1.0.0. Availability below refers to source-scan at product 524fa07e.

V-LIFE-12 — Pointer or count exceeds its valid extent#

Pointer or count exceeds its valid extent. It examines ownership, resource state, and lifetime obligations across program paths.

Availability#

Not available in source-scan. There is no source-scan flag to activate this condition.

Example and action#

Illustrative pattern only. This is not a complete runnable package or a reproduced source-scan result. Helper APIs and omitted context must be supplied by the application.

bytes.withUnsafeBytes { raw in
    consume(raw.baseAddress, count: raw.count + 1)
}

Review the owner, transfer points and every exit path. Keep cleanup obligations and the valid lifetime explicit; avoid introducing a second cleanup or extending an invalid borrow.

bytes.withUnsafeBytes { raw in
    consume(raw.baseAddress, count: raw.count)
}

Intended analysis#

Intended reasoning: Track the resource identity, ownership or valid extent through creation, transfer, use and cleanup events. The intended decision requires evidence that those events refer to the same object and that the relevant paths are covered. Required evidence: ownership, lifetime, allocation, and resource-state facts

Assumptions and unknown#

The relevant facts must be admitted for the selected immutable build world. Unknown aliases, external effects, unsupported source forms or incomplete consumers can prevent a conclusion. Availability in this workflow is stated above; the illustration does not expand that availability.

Evidence and interpretation#

The target catalog describes the intended condition. It is not evidence of an active source-scan diagnostic.

Historical evidence at 4558458d: recovery-required (historical qualification is incomplete and needs further evidence). That evidence has not been requalified for this product revision.

How we validate checks explains the evidence boundary. Foundations separates method assumptions from implementation claims.