Hardware read/write breakpoint not rendered in UI when set on .rdata section (still functional, appears in breakpoint list)

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:

1. Open any binary in Binary Ninja
2. Start a local debug session with "WINDOWS_NATIVE"
3. Set a hardware breakpoint on an address located within the .rdata section
4. 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
5. 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

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.