Skip to content

Report errors when hardware breakpoints fail with LLDB#1035

Open
xusheng6 wants to merge 1 commit intodevfrom
fix_hw_breakpoint_lldb_error
Open

Report errors when hardware breakpoints fail with LLDB#1035
xusheng6 wants to merge 1 commit intodevfrom
fix_hw_breakpoint_lldb_error

Conversation

@xusheng6
Copy link
Copy Markdown
Member

Summary

  • Warn users upfront in the hardware breakpoint dialog when adding a hardware execution breakpoint with LLDB before debugging (it would previously be silently recorded but fail later)
  • Log errors via LogError when deferred hardware breakpoints fail to apply on first stop in the LLDB adapter
  • Log errors in DebuggerBreakpoints::Apply() when hardware breakpoints fail to apply
  • Improve error messages in the dialog: LLDB-specific message links to Hardware execution breakpoint does not work on Linux x86/x64 with LLDB adapter #957, generic message lists possible causes

Test plan

  • With LLDB adapter selected, try adding a hardware execution breakpoint before debugging starts — should show warning dialog
  • With LLDB adapter, add a hardware execution breakpoint during debugging — should show improved error message with link to Hardware execution breakpoint does not work on Linux x86/x64 with LLDB adapter #957
  • With other adapters, hardware breakpoint failures should show improved generic error message
  • Check log output for LogError messages when hardware breakpoints fail to apply

Closes #1034

🤖 Generated with Claude Code

When adding a hardware execution breakpoint with the LLDB adapter before
debugging, the breakpoint was silently recorded but would fail when applied.
Now we warn the user upfront in the dialog, log errors when deferred hardware
breakpoints fail to apply, and provide LLDB-specific guidance linking to #957.

Closes #1034

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adding a hardware execution breakpoint with LLDB before lauching the target silently succeeds but it does not work

1 participant