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
It appears that, in VSCode's builtin debugger, it resolves symlinks for file breakpoints when it decides which file to open showing that the breakpoint was hit. So if I import a header, foo/bar.h which is a symlink to bar.h, and I set a breakpoint in either one, it always moves focus to bar.h when the breakpoint is hit. This would be very helpful in my case (I'm a user of Buck2, which makes lots of header symlinks that I don't want to actually edit while I mess with the breakpoint, I want to edit the original file).
The text was updated successfully, but these errors were encountered:
It appears that, in VSCode's builtin debugger, it resolves symlinks for file breakpoints when it decides which file to open showing that the breakpoint was hit. So if I import a header, foo/bar.h which is a symlink to bar.h, and I set a breakpoint in either one, it always moves focus to bar.h when the breakpoint is hit. This would be very helpful in my case (I'm a user of Buck2, which makes lots of header symlinks that I don't want to actually edit while I mess with the breakpoint, I want to edit the original file).
The text was updated successfully, but these errors were encountered: