Vector35 / Vector35/binaryninja-api
Cross references duplicated and don't display correctly when switching ILs
Nessuno ha ancora preso questa issue.
- Lingua principale
- C++
- Stelle
- 1.3k
- Fork
- 298
- Merge medio
- 5g 5h
- PR unite (30g)
- 19
Descrizione
Version and Platform (required):
- Binary Ninja Version: 4.1.5746
- OS: Ubuntu
- OS Version: 24.04
- CPU Architecture: aarch64
Bug Description:
We now have what appears to be weirdly duplicated cross-references when switching ILs in certain cases? I'm pretty sure that's not actually what's happening, it's just what the effect looks like from a user perspective.
Here's an example in HLIL on 4.0 stable:
When you switch from HLIL to disassembly, it won't change at first, and then will eventually change to this, which is also wrong:
Re-clicking on that address leads to this:
In the new 4.1 stable we're testing, it does this in HLIL:
...which immediately switches to this:
...and clicking on the address again gives this:
Steps To Reproduce:
- Open the binary below
- Navigate to 0x217af4
- Click on
x0 - Observe cross-references
- Change view to Disassembly
- Observe cross-references again
Expected Behavior:
Something closer to what's in 4.0 than 4.1. And, also, showing what I see when I re-click on the address possibly.
Screenshots/Video Recording:
See above.
Binary:
libicui18n.so.70.zip
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Open the supplied libicui18n.so.70 binary in Binary Ninja and reproduce the sequence at 0x217af4: click x0, inspect cross-references, switch from HLIL to Disassembly, and click the address again. Trace the cross-reference display and IL-switch handling; done means references are not duplicated or stale and remain consistent across the views.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp
- Ambito
- reverse-engineering
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100