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
Similar to oracle/graal#5125, core library files won't appear in the "Loaded Scripts" section in the VS Code debugger. You can step into Ruby core library from a user function, which will cause the core library to load in the editor view. But, unlike with standard libraries, setting a breakpoint in this editor will not work when restarting the debugger. As a result, it's rather difficult to debug anything related to the core library.
Are you using --core-load-path in this case or not?
If yes, it's most likely the same as oracle/graal#5125.
If not, then the Source doesn't actually have a file that VSCode can open, it's a file from inside truffleruby.jar, so then it sounds like a VSCode issue.
Activity
eregon commentedon Sep 30, 2022
Are you using --core-load-path in this case or not?
If yes, it's most likely the same as oracle/graal#5125.
If not, then the Source doesn't actually have a file that VSCode can open, it's a file from inside truffleruby.jar, so then it sounds like a VSCode issue.
eregon commentedon Mar 21, 2023
With
--core-load-path
it worked fine when we tried recently, although one needs to first find such file and they are not all in Loaded Scripts.