Debug not stopping on breakpoint

[jcald1]

I'm running ""node v6.5.0"" on Ubuntu using "Eclipse Java EE IDE for Web Developers. Version: Neon Release (4.6.0)" with "Nodeclipse Core and Node.js 1.0.2.201509250223 org.nodeclipse.feature.group Nodeclipse/Enide"

I started the application with the argument "--debug-brk=5858", and I see "Debugger listening on [::]:5858" in the console. The debugger stops on the first line. I hit the green Resume button.

Then I submit my HTTP request and expect the debugger to stop on the breakpoint, which is one line above where an exception is thrown inside a restify handler function. The debugger doesn't stop on the breakpoint.

I tried starting eclipse with "./eclipse -clean" but had no luck.

[paulvi]

Please also try asking on http://stackoverflow.com/questions/tagged/nodeclipse

It seems that you don't know basic Nodeclipse usage http://www.nodeclipse.org/usage
where you just need right click a .js file and Run/Debug as -> Node application
(or you just have those Preferences?)

Again please ask on SO, for bug here there should be a way to reproduce, so share code

[comodoro]

I have the same problem with recent Eclipse Neon
Version: Neon.2 Release (4.6.2)
Build id: 20161208-0600
and Nodeclipse, in Installation Details:
Nodeclipse Core and Node.js 1.0.2.201509250223 org.nodeclipse.feature.group Nodeclipse/Enide

It is a fresh installation. I get why the debugging stops on the first line (although it would make more sense to not do that in the IDE, i.e. start the debugger with --debug instead of --debug-brk), but if I resume or do "Step over" twice, the program continues skipping all breakpoints. Curiously if I do "Step into", the debugging works, but I do not want to debug the request module:)

According to Stack Overflow I am not the first with this problem, but I have found no solution yet. Is it supposed to only work in ENIDE? Because I did not find it explicitely mentioned anywhere.

[bb-work]

I also have the same problem. Node.js application. I am using the Node perspective, and I right-click my application and 'Debug As Node Application'. The application stops on the first line of app.js, but when I set breakpoints in other files, they are not reached. By using console logging, I can see that the code is being executed, but if I'm going to do printf debugging, what's the point of an IDE?

[paulvi]

Help wanted, as I am not using Node.js for a year.

I can give a guide for a person taking closer look, the 1st step would be to confirm that this issue is always the case.