Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Bitfield pointers don't render correctly

未关闭
#8,408 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
cpp

调研方向

Start with StructureMemberLinearViewObject's bitfield-member rendering and compare it with the DataRendererContainer::RenderObjectForData path used by other structure members. Then trace the pointer renderer's handling of bitfield length and the __based pointer; done means the reproduced struct renders foo using its 0x1234 base without consuming bits belonging to bar.

由索引模型根据 Issue 内容生成。

描述

Version and Platform (required):

  • Binary Ninja Version: based on 5.4.10248
  • Edition: Ultimate
  • OS: macOS
  • OS Version: 26.6
  • CPU Architecture: arm64

Bug Description:
When a pointer type is rendered as part of a bitfield structure member, the pointer data renderer is not invoked and details like the pointer base is not handled.

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. Open a new file, enter in bytes 10 00
  2. Create a type with the following signature:
struct struct_1 __packed
{
    void* __ptr16 __based(const, 0x1234) foo : 12;
    int16_t bar : 4;
};
  1. Apply the struct_1 type to the first byte of the binary
  2. Observe the foo member is not rebased as you defined

Expected Behavior:
I expected my pointer base to apply when rendering pointers.

Screenshots/Video Recording:
Image

Additional Information:
This is because StructureMemberLinearViewObject has dedicated behavior for rendering bitfield structure members, and that does not invoke the DataRendererContainer::RenderObjectForData as it does for all other structure members. Even if this were changed, the pointer renderer would need to understand the bitfield length of the member it is rendering, so it does not read the bits shared with other members in the bytes of the rendered member.

主要语言
C++
星标
1.3k
派生
298
平均合并
4 天 13 小时
30 天内合并 PR
20

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Vector35/binaryninja-api 的其他 Issue

查看 Vector35/binaryninja-api 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。