eclipse - Nodeclipse Debugger 在第一行停止，即使在清除所有断点之后也是如此

Question

我认为这是 Eclipse 的 NodeClipse IDE 中的错误。即使在我删除了 IDE 中的所有断点之后，调试器仍然停在第一行，这让我抓狂。一天结束时，我不得不寻找微小的“继续”按钮，这让我失去了耐心。

有人遇到同样的问题吗？你是怎么解决这个问题的？

这是问题的图片:

http://joaorosilva.no-ip.org/public/stackoverflow/Screen%20Shot%202013-07-04%20at%2015.35.37.png

Answer 1

没有“NodeClipse IDE”这样的东西

有

• nodeclipse 插件 (nodeclipse-1)
• Enide(插件集)
• Nodeclipse NTS(Eclipse 发行版)

您应该提到您使用的 Nodeclipse 和 Eclipse 的确切版本。我现在每天都在使用 Nodeclipse NTS 0.4.10(基于 Eclipse 4.3 Kepler)。

只需按 F8 即可继续。

自 Nodeclipse 0.6 以来，有“no -break”选项，这将使用 --debug 而不会在第一行中断 Node 应用程序。

来自 Node 维基

There are 2 debug related node options:

node --debug[=port] NodeApp.js

node --debug-brk[=port] NodeApp.js

The --debug option will just enable remote debugger connection on given port and then start the application normally. Even when debugger is connected to the running node instance later on, the script execution will not be stopped until “Suspend” command is issued by Eclipse debugger. Another way to stop the execution is to browse the source code of the JavaScript modules comprising the application and double click on the line number at the desired position in script to break at (most likely a callback). Once execution stops you can set/clear more breakpoints, but also inspect call stack and view content of all program variables.

The --debug-brk option is needed when your script is short lived (no time to attach debugger) and/or you want to observe the NodeApp.js execution from the very start. This option will force execution to break at the first line of the main script and wait for debugger to connect. The behavior upon connection is now different – the script is suspended and no breakpoints are set. Note that V8 engine debugger is not behaving very good when it steps over or steps into require() method (it will crash), so try to set up first breakpoint past the initial module loading. This will also enable you to set breakpoints in any of those modules as well.

也就是说，如果使用--debug，那么小型应用程序和应用程序的开头是不可能调试的。