Skip to content

Several issues relating to PDB VTables #7827

Open

Description

@trumank

Version and Platform (required):

  • Binary Ninja Version: 5.3.8818-dev, 5e360485
  • OS: arch
  • OS Version: unknown
  • CPU Architecture: x86_64

Bug Description:
I don't where the boundaries between these individual issues lie so here are just my observations trying to get VTables to work:

Test binaries/sources: pdb-vtable.zip

VTables structs are defined without `::` separator which breaks inheritence and references from owning type (fixed in #7825) Image
With the above patch applied, vtable data refs in linear view still do not show structured data until manually redefined Image
With the types manually redefined as the same type (Change Type... Enter) inherited members still do not appear Image
Seems like System Types and Debug Info has diverged? Image Image
Virtual function calls do not resolve in HLIL Image
Parent class gets conflated with namespace and causes VTable name to contain entire class hierarchy
class Level0 {
public:
    int level0_data;

    Level0() : level0_data(0) {}
    virtual ~Level0() { g_sink = 200; }
    virtual void level0Func() { g_sink = 201; }
};

class Level1 : public Level0 {
public:
    int level1_data;

    Level1() : level1_data(1) {}
    ~Level1() override { g_sink = 210; }
    void level0Func() override { g_sink = 211; }
    virtual void level1Func() { g_sink = 212; }
};

class Level2 : public Level1 {
public:
    int level2_data;

    Level2() : level2_data(2) {}
    ~Level2() override { g_sink = 220; }
    void level0Func() override { g_sink = 221; }
    void level1Func() override { g_sink = 222; }
    virtual void level2Func() { g_sink = 223; }
};
Image

Activity

  1. emesare commented on Dec 29, 2025

    @emesare
    Member

    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']
  2. self-assigned this
    on Dec 29, 2025
  3. added
    DebugInfo: PDBRelated to parsing PDB files
    Impact: HighIssue adds or blocks important functionality
    Effort: TrivialIssues require < 1 day of work
    on Dec 29, 2025
  4. added theissue type on Dec 29, 2025
  5. added this to the Jotunheim milestone on Dec 29, 2025
  6. emesare commented on Dec 29, 2025

    @emesare
    Member
    Image

    Test 13 has presumably multiple defs at the data var, where the int32_t vtable type is dangling.

  7. added a commit that references this issue on Dec 29, 2025
  8. modified the milestones: Jotunheim, Krypton on Mar 23, 2026
  9. modified the milestones: Krypton, L on Aug 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

DebugInfo: PDBRelated to parsing PDB filesEffort: TrivialIssues require < 1 day of workImpact: HighIssue adds or blocks important functionality

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions