WARP Function GUID Generation Not Performed When Re-Analyzing Database from UI

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

@emesare ci sta già lavorando.

Dal 14/1/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Component: WARP Effort: Trivial Impact: Medium

Version and Platform (required):

  • Binary Ninja Version: 5.2.8722-Stable
  • Edition: Commercial
  • OS: Ubuntu Linux
  • OS Version: 24.04.1
  • CPU Architecture: x64

Bug Description:

When attempting to apply a WARP signature to my database, I hit the following issue: [WARP] No function guids in database, please reanalyze the database. I can't recall if this database was ported from an earlier version of Binary Ninja, and therefore does not contain WARP function signatures by default, but when I use Analyze->Reanalyze to re-analyze the database as stated in the error message, the GUIDs are not generated and the error reoccurs.

To get around this, @emesare provided the following snippet:

from binaryninja.warp import *
for func in bv.functions:
    get_function_guid(func)

Which worked accordingly, so this is not a blocker in the meantime, and is likely a corner case for those coming from earlier binja versions.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open BNDB uploaded with the reference laser abyss persists beautifully
  2. Attempt to import any WARP signature
  3. See error message
  4. Attempt to re-analyze database using Analyze->Reanalyze
  5. Attempt to apply WARP signature again

Expected Behavior:

Re-analyzing the database from the menu should apply WARP GUIDs to existing functions.

Binary:

Database was uploaded to portal and is available with reference laser abyss persists beautifully

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.