Adding a hardware execution breakpoint with LLDB before lauching the target silently succeeds but it does not work
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Due to https://github.com/Vector35/debugger/issues/957, hardware execution breakpoint does NOT work on Linux with LLDB adapter. If the user attempts to add it during debugging, they will be met with the expected error message:
However, if the user does so before debugging, the breakpoint will be recorded, but then later when the lldb adapter tries to add them, it fails silently, which could cause confusion
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the LLDB adapter path that adds recorded hardware execution breakpoints when debugging begins, and compare it with the path used while a session is already active. Reproduce the behavior on Linux before launching the target, then verify that an unsupported breakpoint produces the expected error instead of being silently accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100