| Previous | Next |
| OSS_LIMITED | OSS_BAD_TIME |
OSS_BAD_PTR
OSS_BAD_PTR (0x8009300B) is an OSS ASN.1 runtime result for unexpected null inside the value graph. The encoder follows a generated pointer that should designate a component or collection element but finds null, indicating an incompletely built object. Because the exact generated member reached before failure is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording presence bits, CHOICE selector, and list counts, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Interpretation at runtime
At the unexpected null inside the value graph boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and ownership and lifetime of nested allocations; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Diagnostic record
- the exact generated member reached before failure
- presence bits, CHOICE selector, and list counts
- ownership and lifetime of nested allocations
Small experiments with high signal
- construct the same value using generated initializers
- walk pointer-bearing fields before encoding
- run the producer under address sanitization or page heap
Avoid the wrong workaround: the result
BAD_ARG concerns parameters passed to the codec; BAD_PTR points inside the ASN.1 value supplied for encoding.
Instrumentation
Where the exact generated member reached before failure can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use presence bits, CHOICE selector, and list counts together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Proof of recovery: the result
Build values through generated APIs, keep selector and presence metadata consistent, and add a structural validation test.
Technical references
Looking for a different code? Search another status or error code.