SysvMessageSerializationMismatch

warning native on by default

Group: Probable bugs

Identify msg_receive when local successful msg_send on same queue and exact positive matching type uses a different serialize flag. Require known flags, no unknown queue operation and no competing-sender evidence; unknown message selection excludes.

Detection

• Report msg_receive when local successful msg_send on same queue and exact positive matching type uses a different serialize flag. Require known flags, no unknown queue operation and no competing-sender evidence; unknown message selection excludes.
• Resolve builtin functions, classes, constants and methods, including imports and supported named arguments. Follow only bounded local facts within one lexical scope. Receiver and argument provenance must establish the specific API contract; variable names and comments never prove intent.
• Report one finding per violating operation. A reachable path, unchanged value identity and applicable API behavior are required. Intervening mutation, unknown calls involving tracked values, escaped aliases or exhausted analysis budgets invalidate proof.

Exceptions (no report)

• Receiving serialized bytes with decoding disabled is valid. Raw payloads with a possible PHP serialization prefix, or unknown payloads, cannot prove a decoding mismatch.

• A flag, message type or payload read from a variable is not a known value once that variable may have been stepped with ++ or --, or captured by reference by a closure, before the call reads it. A step later in a loop that also encloses the read counts too, because the next iteration observes it. A step after the read outside any shared loop, or a by-value capture, leaves the value known.

• Exclude unresolved required symbols, user-defined lookalikes, incomplete syntax, unknown required values and unsupported versions.

• Both @custos-ignore SysvMessageSerializationMismatch and @noinspection SysvMessageSerializationMismatch suppress this native rule.

Fix

None. A repair requires a semantic decision or application error-handling policy.

PHP versions

Available in PHP 5.3–8.5 where the referenced API exists. Do not apply extension contracts when the resolved API is unavailable. Gate syntax and version-specific behavior to the configured target.

Configure

In custos.json:

{
  "rules": {
    "SysvMessageSerializationMismatch": {
      "enabled": false
    }
  }
}

Suppress

Before the statement or declaration (or the first statement of the file):

// @custos-ignore SysvMessageSerializationMismatch