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
Gama11 opened this issue
Feb 14, 2017
· 4 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
As I understand, StackFrame.source in the debug protocol is supposed to be optional (because there might not always be a source location available). However, starting with VSCode 1.9.0, a missing source causes the following error (after a pause request response, might happen elsewhere too):
(btw: same thing with a source that is present, but has no path)
At first glance, this makes it look like pausing didn't work. However, at a second glance, pausing and resuming still works fine, so it's mostly a cosmetic issue (that still might lead the user to think it's broken).
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Feb 15, 2017
nulld
added a commit
to vshaxe/flash-debugger
that referenced
this issue
Feb 15, 2017
@isidorn Yes, it works if our debug adapter sends a stackframe like the one in the screenshot of my original post (one without a source).
Our debug adapter used to send messages like this, where source is present, but path is null - with this, I can still reproduce the error on Insider's:
I just assumed that that was incorrect API usage / not supposed to work anyway - it always showed the path as null in the call stack rather than detecting it as Unknown Source:
Even though in 1.8.1, this didn't error, but it actually opened a <null> file, which doesn't seem correct either:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
As I understand,
StackFrame.source
in the debug protocol is supposed to be optional (because there might not always be a source location available). However, starting with VSCode 1.9.0, a missingsource
causes the following error (after a pause request response, might happen elsewhere too):(btw: same thing with a
source
that is present, but has nopath
)At first glance, this makes it look like pausing didn't work. However, at a second glance, pausing and resuming still works fine, so it's mostly a cosmetic issue (that still might lead the user to think it's broken).
Here's what our debug adapter (Haxe Debug) sends:
This works fine (no error appears) in 1.8.1, which would make this a regression. The issue is still present in the latest Insider's build (1d17b45).
Other debug adapters seem to have the same issue, as suggested by this StackOverflow question regarding the same error message with ASP.NET.
Issue #4608 seems somewhat related to this.
The text was updated successfully, but these errors were encountered: