search

c9 / c9.ide.run.debug

The repository for c9.ide.run.debug, a Cloud9 core plugin
https://c9.io/packages/c9.ide.run.debug
Other
13 stars 16 forks source link

Breakpoints moving to incorrect location with babel #35

Open conradob opened 8 years ago

conradob commented 8 years ago

Already tested in 2 Macbook Pro with OS X and Linux Ubuntu.

In Ubuntu 14 (also Xubuntu) with Node 4.4 breakpoints work properly. breakpointworking_linuxubuntu

The problem occur in OS X also with Node 4.4 where breakpoints are moving to incorrect line number only when I run the application in debug mode. breakpointproblem_macos I would like to understand why it's not working properly only in Mac OS.

nightwing commented 8 years ago

V8 changes the line of the breakpoint when it cannot set it on the requested line. Cloud9 passes some flags to node to disable some optimizations that interfere with breakpoints https://github.com/c9/c9.ide.run/blob/master/runners/Node.js.run#L1 This issue can be caused by either node itself not working well on mac os, or cloud9 runner not passing correct arguments. Could you try changing

"${debug?`node --version | grep -vqE \"v0\\..\\.\" && echo --nodead_code_elimination`}",

to

"${debug?--nodead_code_elimination}",
conradob commented 8 years ago

I got it, but I'm still facing the issue.

Currently we are developing using Babel, do you believe that this code structure could be the problem?

nightwing commented 8 years ago

Babel can be a problem since we do not support source maps yet.

conradob commented 8 years ago

Is there any development for this feature?