You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First breakpoint is skipped on a remote development environment #900
{
// Use IntelliSense to learn about possible attributes.// Hover to view descriptions of existing attributes.// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387"version": "0.2.0",
"configurations": [
{
"type": "rdbg",
"name": "Run the current file with rdbg",
"useBundler": true,
"request": "launch",
"command": "ruby",
"script": "${file}",
},
]
}
Create the following in test.rb.
a=1binding.bbinding.b
Ensure v0.1.0 of the vscode-rdbg extension is installed.
Switch to test.rb and choose "Run the current file with rdbg". Observe that it correctly stops at the first breakpoint.
Stop the debugger.
Add sleep 1 on a new line after a=1
Choose "Run the current file with rdbg" again.
Observe that it incorrectly skips the first breakpoint and stops at the second.
changed the title [-]First breakpoint is skipped when running via `bin/rails runner` on a remote development environment[/-][+]First breakpoint is skipped[/+]on Feb 17, 2023
Activity
[-]First breakpoint is skipped when running via `bin/rails runner` on a remote development environment[/-][+]First breakpoint is skipped[/+][-]First breakpoint is skipped[/-][+]First breakpoint is skipped on a remote development environment[/+]andyw8 commentedon Feb 23, 2023
Some further findings on this:
It seems like a race condition. If I add
sleep 0.1before this line:debug/lib/debug/server.rb
Line 350 in d7bf3b2
then it stops at the first breakpoint.
I'm wondering if could relate to #131
Also:
useTerminalis enabled.(cc @st0012)
andyw8 commentedon Feb 23, 2023
Additionally, if I set this to
false, it seems to illustrate that it does stop on the first breakpoint, but immediately continues.