In the previous section of this tutorial, we discussed the "launch" configuration, but the rdbg program also supports the "attach" configuration. If you're having trouble getting the "launch" configuration to work properly, I suggest trying the "attach" configuration instead as described in the next section. I'll take about how to do that in a future tutorial 😁. Pretty cool! It's like we're debugging JavaScript using Chrome DevTools! Actually, the rdbg debugger can be attached to Chrome, so we can inspect Ruby code from within Chrome DevTools. We can also hover over variable names or method parameters to see what their current values are. Just click to the left of a line number in main.rb to insert a new breakpoint.Īs shown above, VS Code provides a "variables" section where we can see the values of each variable inside our program while it is running. Select "Debug current file with rdbg" from the dropdown menu and click on the green arrow to start the debugger! If all goes well, you should be able to debug in VS Code! You can add breakpoints anywhere in the code like you normally would with a JavaScript debugger. Next to "RUN AND DEBUG," you should see a green arrow and a dropdown menu. Alternatively, you can use the Command + Shift + D keyboard shortcut to navigate to this view.
Click on it to navigate to the "Run and Debug" view. Then, on the Primary Side Bar (left side bar) of VS Code, you should see a symbol that looks like a triangle with a bug icon on top.
Navigate to the main.rb file from within VS Code. This configuration lets us run the Ruby debugger with a click of a button from within VS Code. We'll look at the "Launch" configuration first. Launch (named "Debug current file with rdbg").As you may have noticed in the launch.json file, there are two configurations we can use when launching the Ruby debugger, rdbg, with VS Code: Let's now talk about the different ways of activating the debugger. If useBundler was set to true, then the Ruby debugger VS Code extension would run Ruby scripts using bundle exec and end up executing Ruby scripts using something like bundle exec ruby main.rb. This means that we can expect the Ruby debugger VS Code extension to execute Ruby scripts using something like ruby main.rb Notice how the useBundler option is set to false and the command is set to ruby.
0 kommentar(er)
