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 摘要。