Question

Im evaluating the Geddy MVC framework for node.js and I am seeing a strange issue – none of my breakpoints get hit when debugging.

I am using WebStorm to launch node.js in debug mode.

I dont know how to make Geddy start in debug mode using the CLI command so I have a bootstrapper file that I use that looks like this:

console.log("Starting server...")
var geddy = require("geddy/bin/cli")
console.log("Server started.")

I set a breakpoint on all three lines and only the last console.log gets hit, so at least I know that the breakpoints and debugging is working properly.

Geddy internally require()‘s my controllers who also have breakpoints set in several locations. These never get hit, but the controllers do work properly and the HTTP requests are served properly as well.

Is there any reason why breakpoints will not be hit in Geddy? Is there something more I can do?

Answer 1

I have been unable to verify this, but I believe the issue is due to the fact that cluster spawns new processes but the debugger is unaware of them. I have not found a way to attach the debugger to the new processes, and im not even sure if they can be started with the debugging port open.

Geddy uses cluster so it inherits this issue.

This thread mentions a possible solution:
( How do I enable –debug for node.js when running GeddyJS ) but this did not help me.