API for persistent tags or metadata on local and parameter variables

未關閉
#8,724 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp

研究方向

Start by reading the public API definitions and documentation for variables, BinaryView metadata, and tags to see how variable identities are represented and persisted. The issue does not name specific files or tests; trace the relevant API entry points and existing persistence tests. Done means plugins can attach, retrieve, and remove persistent metadata on local and parameter variables, with documented behavior when reanalysis changes variables.

由索引模型根據 Issue 內容生成。

描述

What is the feature you'd like to have?

An API to attach, retrieve, and remove persistent annotations on individual local and parameter variables. A string value would be sufficient, including a JSON string for structured information. The annotations should survive saving and reopening the BNDB.

Native variable tags would be useful, but arbitrary per-variable metadata would also meet my needs.

Is your feature request related to a problem?

I’m building analysis tooling that recovers variable names and types. I’d like to record why I’m confident, or uncertain, that a particular local or parameter is correctly named or typed, including the source of that information and supporting evidence.

Function-level tags are too coarse, and address tags annotate an instruction rather than the variable itself. Putting this information into variable names would clutter the analysis.

Are any alternative solutions acceptable?

Yes. An officially supported way to associate persistent metadata with a variable would be sufficient; it doesn’t have to use the existing tag system.

BinaryView-level metadata with a custom variable-keying scheme is a possible workaround, but it leaves plugins responsible for maintaining the association as variables change during analysis.

Additional Information:

For example, an annotation could contain:

{
  "property": "type",
  "confidence": "tentative",
  "source": "analysis-plugin",
  "reason": "Matches observed field accesses; not independently verified"
}

This is explanatory metadata, separate from Binary Ninja’s existing analysis-confidence values. Documented behavior when variables are split, merged, or removed during reanalysis would also be helpful.

主要語言
C++
星號
1.3k
分支
304
平均合併
2 天 20 小時
30 天內合併 PR
10

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Vector35/binaryninja-api 的其他 Issue

查看 Vector35/binaryninja-api 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。