Several issues relating to PDB VTables

Aperta
#7,827 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@emesare ci sta già lavorando.

Dal 29/12/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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) 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
Lingua principale
C++
Stelle
1.3k
Fork
298
Merge medio
5g 5h
PR unite (30g)
19

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Vector35/binaryninja-api

Tutte le issue di Vector35/binaryninja-api

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.