Several issues relating to PDB VTables

Open

#7,827 opened on Dec 23, 2025 2 comments 0 reactions 1 assignee View on GitHub

@emesare is already working on this.

Since Dec 29, 2025.

Assessment

This issue has not been assessed yet.

Description

DebugInfo: PDB Effort: Trivial Impact: High

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)

With the above patch applied, vtable data refs in linear view still do not show structured data until manually redefined

With the types manually redefined as the same type (Change Type... Enter) inherited members still do not appear

Seems like System Types and Debug Info has diverged?

Virtual function calls do not resolve in HLIL

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; }
};

Dominant language: C++
Stars: 1.3k
Forks: 298
Avg merge: 5d 5h
Merged PRs (30d): 19

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Eval bug: SIGSEGV in token-counting routes when the request arrives while the server is sleeping (stale vocab/mctx captured before the wake barrier) Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

ggml-org/llama.cpp#29188 · Opened Sep 20, 2026
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

gazebosim/gz-sensors#662 · 1 comment · Opened Sep 20, 2026
Aligned columns on the serial monitor while keeping CSV on the SD card Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

NorthernWidget/Margay_Library#31 · Opened Sep 20, 2026
v1 manifest list: existing_files_count is the table-wide total-data-files Open

comp-datalake

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

ClickHouse/ClickHouse#121222 · Opened Sep 20, 2026
Case collision between `Canvas` and `canvas` test directories causes platform-dependent source hashes Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

LadybirdBrowser/ladybird#12123 · Opened Sep 20, 2026

More C++ issues