aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineCopyPropagation.cpp
diff options
context:
space:
mode:
authorWalter Erquinigo <a20012251@gmail.com>2024-07-10 19:05:38 -0400
committerGitHub <noreply@github.com>2024-07-10 19:05:38 -0400
commit541f22ee361a8b3029ac898db29d3e9184fb1671 (patch)
tree2be5eeab8b5d14d95231c503a9e5d3cfbd24c495 /llvm/lib/CodeGen/MachineCopyPropagation.cpp
parented09637c496dee37b23d73040dff6f7a4805c53a (diff)
downloadllvm-541f22ee361a8b3029ac898db29d3e9184fb1671.zip
llvm-541f22ee361a8b3029ac898db29d3e9184fb1671.tar.gz
llvm-541f22ee361a8b3029ac898db29d3e9184fb1671.tar.bz2
[lldb-dap] Support throw and catch exception breakpoints for dynamica… (#97871)
…lly registered languages First of all, this is done to support exceptions for the Mojo language, but it's done in a way that will benefit any other plugin language. 1. I added a new lldb-dap CLI argument (not DAP field) called `pre-init-commands`. These commands are executed before DAP initialization. The other `init-commands` are executed after DAP initialization. It's worth mentioning that the debug adapter returns to VSCode the list of supported exception breakpoints during DAP initialization, which means that I need to register the Mojo plugin before that initialization step, hence the need for `pre-init-commands`. In general, language plugins should be registered in that step, as they affect the capabilities of the debugger. 2. I added a set of APIs for lldb-dap to query information of each language related to exception breakpoints. E.g. whether a language supports throw or catch breakpoints, how the throw keyword is called in each particular language, etc. 3. I'm realizing that the Swift support for exception breakpoints in lldb-dap should have been implemented in this way, instead of hardcoding it.
Diffstat (limited to 'llvm/lib/CodeGen/MachineCopyPropagation.cpp')
0 files changed, 0 insertions, 0 deletions