go-delve/delve · error

unable to parse breakpoint hit condition: %q hit conditions

Error message

unable to parse breakpoint hit condition: %q
hit conditions should be of the form "number" or "OP number"

What it means

Error "unable to parse breakpoint hit condition: %q hit conditions should be of the form "number" or "OP number"" thrown in go-delve/delve.

Source

Thrown at pkg/proc/target_group.go:500

	if lbp.enabled {
		switch {
		case lbp.condSatisfiable && !breakpointConditionSatisfiable(grp.LogicalBreakpoints, lbp):
			lbp.condSatisfiable = false
			grp.disableBreakpoint(lbp)
		case !lbp.condSatisfiable && breakpointConditionSatisfiable(grp.LogicalBreakpoints, lbp):
			lbp.condSatisfiable = true
			grp.enableBreakpoint(lbp)
		}
	}

	return nil
}

func parseHitCondition(hitCond string) (token.Token, int, error) {
	match := hitConditionRegex.FindStringSubmatch(strings.TrimSpace(hitCond))
	if match == nil || len(match) != 6 {
		return 0, 0, fmt.Errorf("unable to parse breakpoint hit condition: %q\nhit conditions should be of the form \"number\" or \"OP number\"", hitCond)
	}

	opStr := match[1]
	var opTok token.Token
	switch opStr {
	case "==", "":
		opTok = token.EQL
	case ">=":
		opTok = token.GEQ
	case "<=":
		opTok = token.LEQ
	case ">":
		opTok = token.GTR
	case "<":
		opTok = token.LSS
	case "%":
		opTok = token.REM
	case "!=":

View on GitHub (pinned to a23773e6c3)

When it happens

Trigger: Thrown at pkg/proc/target_group.go:500 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Parsing and encoding errors: unexpected token, malformed input — why parsers reject input and how to find the real culprit.

AI-assisted analysis of go-delve/delve@a23773e6c3 (2026-08-31). Data as JSON: /api/errors/ed173ef91731ce82. Report an issue: GitHub.