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

Abierto
#7,865 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@emesare ya está trabajando en esto.

Desde el 14/1/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
C++
Estrellas
1.3k
Forks
298
Merge medio
5 d 5 h
PR fusionados (30 d)
19

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Vector35/binaryninja-api

Todos los issues de Vector35/binaryninja-api

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.