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
Fix for vscode-powershell #837 callstack missing line info.
This PR addresses two bugs. First the missing line info was due to use passing back null when we didn't have end line/col info. The protocol claims that should work. But when I changed the end line/col to reflect the same values as the start line/col (assuming the end values were null - not set) then the callstack started to display the line info. It is a bit weird but the very first frame in some cases contains a col other than 0.
The second bug was that the call stack was getting duplicated. I implemented the new stackTraceRequest for paging stack frames back to VSCode and now that bug is fixed.
I tried to implement StackFrame.PresentationHint == "subtle" for script outside the initial working directory. Do you have a better way to get the workspaceRoot path in the debugger? I had to cache the working dir when SetWorkingDirectory() gets called. And when you attach to a process, there isn't a way to set the "cwd".
Finally, I ran into one bug I'll file later that has to do with the base of the call stack sometimes showing "<ScriptBlock> <No File> 1". If you click on that you get an error telling you <No File> can't be opened.
0 commit comments