aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorStephen Tozer <stephen.tozer@sony.com>2025-07-22 12:43:08 +0100
committerGitHub <noreply@github.com>2025-07-22 12:43:08 +0100
commitd54400559bb6181566030d5f99c6716ea2b2f0a9 (patch)
tree2a7b43efea047b6e82b6556da3ff333b6c001804 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parente96230607cad9d30670ce55ef1cb9dd3fe1e21d7 (diff)
downloadllvm-d54400559bb6181566030d5f99c6716ea2b2f0a9.zip
llvm-d54400559bb6181566030d5f99c6716ea2b2f0a9.tar.gz
llvm-d54400559bb6181566030d5f99c6716ea2b2f0a9.tar.bz2
[lldb-dap] Allow returning multiple breakpoints in "stopped" event (#149133)
Currently, the "stopped" event returned when a breakpoint is hit will always return only the ID of first breakpoint returned from `GetStopReasonDataAtIndex`. This is slightly different from the behaviour in `lldb`, where multiple breakpoints can exist at a single instruction address and all are returned as part of the stop reason when that address is hit. This patch allows all multiple hit breakpoints to be returned in the "stopped" event, both in the hitBreakpointIds field and in the description, using the same formatting as lldb e.g. "breakpoint 1.1 2.1". I'm not aware of any effect this will have on debugger plugins; as far as I can tell, it makes no difference within the VS Code UI - this just fixes a minor issue encountered while writing an `lldb-dap` backend for Dexter.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions