`__attr` attributes on pointer types are lost on save/load

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

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
55/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp, python
領域
backend, databases

研究方向

Start with the Python reproducer in the issue: parse int * __attr("key", "val"), add the type to a TypeArchive, and compare it before and after retrieving it. Trace how pointer and reference type attributes are serialized and restored, then find the relevant tests for type archives. Done means the archived type retains its __attr and the reproducer passes.

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

描述

Version and Platform (required):

  • Binary Ninja Version: 6.1.10984-dev
  • Edition: Commercial
  • OS: macOS
  • OS Version: 27.0.1 (26A434)
  • CPU Architecture: arm64

Bug Description:
In various cases when saving and loading, __attr attributes are lost on pointer and reference types.

Steps To Reproduce:
Run the following reproducer. (This uses a TypeArchive for simplicity, but the same behavior occurs when when defining a type in a database and saving and loading.)

from binaryninja import Platform, TypeParser, TypeArchive
platform = Platform['linux-x86_64']
(qnt, ty), errors = TypeParser.default.parse_type_string('int * __attr("key", "val")', platform)
assert len(errors) == 0
archive = TypeArchive.create('test.bnta', platform)
archive.add_type('test', ty)
print('before archive:', ty)
print('after archive:', archive.get_type_by_name('test'))

Output:

before archive: int32_t* __attr("key", "val")
after archive: int32_t*

Expected Behavior:
The __attr should still be there after archiving.

Additional Information:

  • The bug doesn't occur if you replace int * with, say, int (or apparently any type other than a pointer or reference).

  • This bug was discovered by AI but I vouch for the report.

主要語言
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 摘要。