-
Hi! Didn't know where else to ask. Not sure if I'm doing something wrong or if it was never designed to work this way, but I can manage to connect to the debugger just fine, but when I set a breakpoint on the IDE the execution doesn't stop. It does stop and displays the debugger interface correctly when I write My launch.json is pretty basic. {
"version": "0.2.0",
"configurations": [
{
"type": "ruby_lsp",
"name": "Attach to debugger",
"request": "attach",
"debugHost": "127.0.0.1",
"debugPort": 2324
}
]
} And my app is started with |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Thanks for the question. If the extension has managed to connect to the debugger, then this is probably an issue in One known bug that I'm aware of is |
Beta Was this translation helpful? Give feedback.
Thanks for the question. If the extension has managed to connect to the debugger, then this is probably an issue in
ruby/debug
itself. The Ruby LSP only includes a client to connect to the debugger, it does not implement the DAP server, that's all in theruby/debug
gem.One known bug that I'm aware of is
ruby/debug
doesn't support multiple processes, which has similar symptoms as the ones you're describing (not hitting breakpoints). So if you have your web server configured to use multiple workers, that's likely the issue. If that's not it, please askruby/debug
.