[szokeasaurusrex]

Define v9::raw::Type::UNKNOWN (u32::MAX) alongside Type::VOID (u32::MAX - 1) and use Type::UNKNOWN in SymCacheConverter when a variable or referenced type cannot be resolved.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[vjeranc]

Late to the party, but the void/unknown split requires checking every path that previously conflated the two. Reading this now, to_type_ref() returns None for unsupported references too, which now gets interpreted as void*. We should distinguish an absent DW_AT_type from a present reference we can’t resolve.

It looks like the original Void enum implementation in #1100 avoided this bug: an absent attribute kept the explicit void reference, while an unsupported reference became None and returned unknown. The distinction appears to have been lost in the rewrite to Option<TypeRef>.

[szokeasaurusrex]

@vjeranc I believe your concern should be addressed by 3b8f1a6 on #1100