You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VTables structs are defined without `::` separator which breaks inheritence and references from owning type (fixed in #7825)With the above patch applied, vtable data refs in linear view still do not show structured data until manually redefinedWith the types manually redefined as the same type (Change Type... Enter) inherited members still do not appearSeems like System Types and Debug Info has diverged?Virtual function calls do not resolve in HLILParent class gets conflated with namespace and causes VTable name to contain entire class hierarchy
Most of this is related to qualified names, we plan on removing it (replaced with a single string) because it causes issues like this. The reason the type shows up when you manually redefine the vtable is because qualified names do not round trip.
>>> current_data_var.type.name.name
['Base', 'VTable']
>>> # Redefine the type via UI
>>> current_data_var.type.name.name
['Base::VTable']
Activity
emesare commentedon Dec 29, 2025
Most of this is related to qualified names, we plan on removing it (replaced with a single string) because it causes issues like this. The reason the type shows up when you manually redefine the vtable is because qualified names do not round trip.
>>> current_data_var.type.name.name ['Base', 'VTable'] >>> # Redefine the type via UI >>> current_data_var.type.name.name ['Base::VTable']emesare commentedon Dec 29, 2025
Test 13 has presumably multiple defs at the data var, where the int32_t vtable type is dangling.
[PDB] Remove `QualifiedName` state