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
jrieken opened this issue
Apr 26, 2016
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-priorityverifiedVerification succeeded
let v = process.version;
console.log(v);
let buffer = new ArrayBuffer(320000);
console.log('byte buffer', buffer.byteLength);
let view = new Int32Array(buffer);
console.log('int32 view', view.length);
for (let i = 0; i < view.length; i++) {
view[i] = i * 2;
}
console.log('made it...');
put a breakpoint on the first and last line
run, break, steps until the for-loop, hint continue to run the last statement
⚡ eventually I get told that nodejs isn't responding anymore, debugging is in a weird state like Continue, Stepping being enabled but dysfunctional
The text was updated successfully, but these errors were encountered:
jrieken
added
bug
Issue identified by VS Code Team member as probable bug
important
Issue identified as high-priority
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Apr 26, 2016
@jrieken assigning back to you to retest this scenario with a newer Alpha build that includes our node-debug fix to actually enable debug injection for Electron.
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 issuesimportantIssue identified as high-priorityverifiedVerification succeeded
#4951
yo code
The text was updated successfully, but these errors were encountered: