go-delve/delve · error
could not find hardware breakpoint for address %#x
Error message
could not find hardware breakpoint for address %#x
What it means
Error "could not find hardware breakpoint for address %#x" thrown in go-delve/delve.
Source
Thrown at pkg/proc/native/threads_linux_arm64.go:143
var siginfo ptraceSiginfoArm64
var err error
t.dbp.execPtraceFunc(func() {
_, _, err = syscall.Syscall6(syscall.SYS_PTRACE, sys.PTRACE_GETSIGINFO, uintptr(t.ID), 0, uintptr(unsafe.Pointer(&siginfo)), 0, 0)
})
if err != syscall.Errno(0) {
return nil, err
}
if siginfo.signo != uint32(sys.SIGTRAP) || (siginfo.code&0xffff) != _TRAP_HWBKPT {
return nil, nil
}
for _, bp := range t.dbp.Breakpoints().M {
if bp.WatchType != 0 && siginfo.addr >= bp.Addr && siginfo.addr < bp.Addr+uint64(bp.WatchType.Size()) {
return bp, nil
}
}
return nil, fmt.Errorf("could not find hardware breakpoint for address %#x", siginfo.addr)
}
func (t *nativeThread) writeHardwareBreakpoint(addr uint64, wtype proc.WatchType, idx uint8) error {
wpstate, err := t.getWatchpoints()
if err != nil {
return err
}
if idx >= wpstate.num {
return errors.New("hardware breakpoints exhausted")
}
const (
readBreakpoint = 0x1
writeBreakpoint = 0x2
lenBitOffset = 5
typeBitOffset = 3
privBitOffset = 1
)View on GitHub (pinned to a23773e6c3)
When it happens
Trigger: Thrown at pkg/proc/native/threads_linux_arm64.go:143 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of go-delve/delve@a23773e6c3 (2026-08-31).
Data as JSON: /api/errors/87742f04a2371451.
Report an issue: GitHub.