Vector35 / Vector35/binaryninja-api

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

Open
#7,865 0 comments 0 reactions 1 assignee View on GitHub

@emesare is already working on this.

Since Jan 14, 2026.

Component: WARP Effort: Trivial Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

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

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.