Skip to content

Instantly share code, notes, and snippets.

@focusaurus
Last active October 23, 2017 18:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save focusaurus/3220ec572d3df11e8ca719254b056a7c to your computer and use it in GitHub Desktop.
Save focusaurus/3220ec572d3df11e8ca719254b056a7c to your computer and use it in GitHub Desktop.
node --inspect bugs

Call Stack Expanding: Summary

When debugging node.js via devtools and --inspect, the devtools "Call Stack" accordian panel expands automatically, forcing the "Scope" panel out of the viewable area.

Versions

  • macOS 10.13
  • node v6.11.4, node v6.11.3
  • Chrome 62.0.3202.62, Chrome 61.0.3163.100

Steps to reproduce

  • Launch a simple test program with node --inspect --debug-brk
console.log("Collapse the call stack panel at program start");
setTimeout(() => {
  console.log("Set a breakpoint on this line");
}, 1000);
  • In devtools, set a breakpoint for code not yet hit
  • collapse the "Call Stack" panel
  • Click Play
  • When the breakpoint is hit, the "Call Stack" panel expands automatically

Related Chromium Bugs

  • 656109 Closed Dec 2016
  • 766086 Same issue regressed. Still open.

Console Not Printing: Summary

Using the console with code such as console.log(42) does not print anything to the console.

versions

  • macOS 10.13
  • node v6.11.4
  • chrome 62.0.3202.62

Steps to reproduce

  • debug any node program
  • use the devtools console to try to log anything such as console.log(42)
  • expected: console prints the value
  • actually: console clears without printing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment