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

{ Does not return } harmful assumption

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

还没有人认领这个 Issue。

评估

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

调研方向

Reproduce the issue in Binary Ninja 5.3.9757 on Windows 10 x86_64 using a function with an indirect call through a dynamically set vector. Trace why disassembly stops at the call and identify how valid instructions after it are handled; done means the function's decodable instructions are disassembled without the "{ Does not return }" shortcut.

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

描述

Version and Platform (required):

  • Binary Ninja Version: 5.3.9757 free, a99f2380
  • OS: windows
  • OS Version: 10
  • CPU Architecture: x86_64

Bug Description:

Every time you encounter an indirect call via a dynamically set vector (I'm not sure of the exact conditions but I'm sure you know what I'm talking about) you stop disassembling past the call assuming that it will not return. you only put "{ Does not return }".

This leaves a lot of useful and actually running opcodes not decoded and makes static analysis harder for no reason. Forces me to have to paste the hex code into another tool for disassembly.

Expected Behavior:

Please disassemble the entirety of the functions without any "{ Does not return }" short cuts.

Omitting valid and decodable content for ANY reason is a bad idea.

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