Hardware read/write breakpoint not rendered in UI when set on .rdata section (still functional, appears in breakpoint list)
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 55/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 冷清
- 技術堆疊
- cpp
研究方向
Start by reproducing the issue with a local WINDOWS_NATIVE debug session and a hardware breakpoint on an address in the .rdata section. Compare the disassembly/hex view rendering with the Breakpoints list panel and with breakpoints in other sections. Done means the marker appears at the correct address while the breakpoint still triggers during execution.
由索引模型根據 Issue 內容生成。
描述
Version and Platform (required):
- Binary Ninja Version: 6.0.10474-dev Ultimate (c9ea4d90)
- OS: Windows 11 Pro
- OS Version: 10.0.26200 (Build 26200)
- CPU Architecture: x64 (AMD64 Family 25 Model 97, running under QEMU/Proxmox virtualization)
- Local or Remote Debugging: Local
Bug Description:
When setting a hardware breakpoint on an address within the .rdata section, the breakpoint marker is not rendered in the disassembly/hex view UI. The breakpoint does correctly appear in the Breakpoints list panel, and it still triggers normally during execution. This appears to be purely a UI rendering issue in the disassembly/hex view, not a functional problem with the debugger.
Steps To Reproduce:
- Open any binary in Binary Ninja
- Start a local debug session with "WINDOWS_NATIVE"
- Set a hardware breakpoint on an address located within the .rdata section
- Observe that the breakpoint appears correctly in the Breakpoints list panel, but no breakpoint marker is rendered at that address in the disassembly/hex view
- Run/continue execution — confirm the breakpoint is still hit despite the missing visual indicator
Expected Behavior:
The hardware breakpoint marker should render in the disassembly/hex view at the corresponding address in the .rdata section, consistent with how breakpoints render in other sections.
Screenshots/Video Recording:
Binary:
Additional Information:
System info (via systeminfo):
- Host: DESKTOP-01C7LS4
- System Manufacturer/Model: QEMU Standard PC (Q35 + ICH9, 2009) — running in a virtualized environment (Proxmox)
- BIOS: Proxmox distribution of EDK II 4.2025.02-4~bpo12+1
- Total Physical Memory: 8,152 MB
- Hyper-V/virtualization-based security: Not enabled; hypervisor detected
- 主要語言
- C++
- 星號
- 342
- 分支
- 34
- 平均合併
- 7 天 21 小時
- 30 天內合併 PR
- 1
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
Vector35/debugger 的其他 Issue
-
bug Effort: Trivial
難度 2/5 1-3 小時 新手友好度 68/100
-
bug Effort: Trivial Impact: Low
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 1/5 1 小時以內 新手友好度 95/100
-
Effort: Trivial enhancement UI
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 68/100
查看 Vector35/debugger 的全部 Issue
相似的 Issue
-
Bug Core VIF
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 80/100
ESPresense/ESPresense#2680 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1 小時以內 新手友好度 75/100
stew675/llama-cpp-rdna-boosts#348 ·
維護者通常 1 天內回覆
-
Documentation: Add comprehensive newcomer onboarding guide, project structure, and local usage to README可能已有人在做 @Ash-Blanc 今天認領。 未關閉area/other status/bot-triaged status/need-triage
難度 2/5 半天 新手友好度 85/100
-
bug
難度 1/5 1 小時以內 新手友好度 85/100
維護者通常 1 天內回覆