Skip to content

Commit a12742a

Browse files
paulvipaulvi
committed
add Run and Debug issues to Help
1 parent f1dee7a commit a12742a

File tree

4 files changed

+37
-1
lines changed

4 files changed

+37
-1
lines changed

‎org.nodeclipse.help/contents/.debug.md.html‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
<html>
33
<head>
44
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
5-
<title>C:\Users\weibl\git\Enide-nodeclipse-1\org.nodeclipse.help\contents\.debug.md.html</title>
5+
<title>D:\Workspaces\Nodeclipse-DEV\nodeclipse-1\org.nodeclipse.help\contents\.debug.md.html</title>
66

77

88
<style type="text/css">
@@ -454,6 +454,8 @@ <h2> <a name="debugging" class="anchor" href="..md.html#debugging"><span class="
454454
<p>Right-click <code>.js</code> file with Node.js app and select &quot;Debug As -&gt; Node Application&quot; (similar to Java applications).</p>
455455
<p>Notice that Nodeclipse by default enters step-by-step debugging mode from very first line. Press <kbd>F8</kbd> to continue until breakpoint is reached.</p>
456456
<p>Press <kbd>F11</kbd> to launch debug [again].</p>
457+
<h3> <a name="debugging-issues" class="anchor" href="..md.html#debugging-issues"><span class="octicon octicon-link"></span></a>Debugging issues</h3>
458+
<p>see also Run page.</p>
457459
<h3> <a name="debug-brk-option" class="anchor" href="..md.html#debug-brk-option"><span class="octicon octicon-link"></span></a>debug-brk option</h3>
458460
<p>By default Nodeclipse stops on the first line when debugging. The cause is that V8 remote debugger needs some time (~100ms) to connect to Node.js and get actual modules loaded in V8.</p>
459461
<p>Since Nodeclipse 0.6 there is option &quot;Node debug no -break:&quot; in Preferences to disable interruption at first line. It is good when your application is web server and you don't need to debug initialization lines, but mostly request handlers. </p>

‎org.nodeclipse.help/contents/.run.md.html‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -453,6 +453,12 @@
453453
<h2> <a name="running" class="anchor" href="..md.html#running"><span class="octicon octicon-link"></span></a>Running</h2>
454454
<p>Right-click <code>.js</code> file with Node.js app and select &quot;Run As -&gt; Node Application&quot; (similar to Java applications).</p>
455455
<p>Press <kbd>Ctrl+F11</kbd> to run [again].</p>
456+
<h3> <a name="running-issues" class="anchor" href="..md.html#running-issues"><span class="octicon octicon-link"></span></a>Running issues</h3>
457+
<ul>
458+
<li> <p><a href="https://github.com/Nodeclipse/nodeclipse-1/issues/72">#72 All nodejs apps fail to run (JDK 6 only?)</a> is related to Eclipse and Java version that you use, so updating them would solve. Quote bjm88: </p> <p>Ok working now for me. It does seem you have to uninstall nodeclipse then do Java 7 update ( i tried jre 64 bit and jdk 32 bit, both ok), and set that new java 7 in your eclipse.ini file (format is important). Then reinstall nodeclipse and it will work. Example eclipse.ini entry: -vm C:/dev/java7/bin/javaw.exe -vmargs -Xms128m -Xmx1024m</p> </li>
459+
<li> <p><a href="https://github.com/Nodeclipse/nodeclipse-1/issues/107">#107 Failed to connect to Standalone V8 VM</a> even on JDK 1.6.0_30 was solved by running <code>node --debug-brk app.js</code> first. Quote haroldjiang:</p> <p>yes,the solution is to run node --debug-brk app.js first.</p> </li>
460+
</ul>
461+
<p>see also Debug page.</p>
456462
<h3> <a name="run-configuration" class="anchor" href="..md.html#run-configuration"><span class="octicon octicon-link"></span></a>Run Configuration</h3>
457463
<p>You can configure node and apps parameters workspace wide in <code>Preferences -&gt; Nodeclipse</code> or per file:</p>
458464
<p>Right-click <code>.js</code> file with Node.js app and select &quot;Run As -&gt; Run Configuration...&quot; (Hint: the easiest way to create LaunchConfiguration is actually run the file once.)</p>

‎org.nodeclipse.help/contents/debug.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,12 @@ Notice that Nodeclipse by default enters step-by-step debugging mode from very f
1010

1111
Press <kbd>F11</kbd> to launch debug [again].
1212

13+
### Debugging issues
14+
15+
16+
17+
see also Run page.
18+
1319
### debug-brk option
1420

1521
By default Nodeclipse stops on the first line when debugging. The cause is that V8 remote debugger needs some time (~100ms)

‎org.nodeclipse.help/contents/run.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,28 @@ Right-click `.js` file with Node.js app and select "Run As -> Node Application"
77

88
Press <kbd>Ctrl+F11</kbd> to run [again].
99

10+
### Running issues
11+
12+
- [#72 All nodejs apps fail to run (JDK 6 only?)](https://github.com/Nodeclipse/nodeclipse-1/issues/72)
13+
is related to Eclipse and Java version that you use, so updating them would solve. Quote bjm88:
14+
15+
Ok working now for me. It does seem you have to uninstall nodeclipse then do Java 7 update ( i tried jre 64 bit and jdk 32 bit, both ok),
16+
and set that new java 7 in your eclipse.ini file (format is important). Then reinstall nodeclipse and it will work.
17+
Example eclipse.ini entry:
18+
-vm
19+
C:/dev/java7/bin/javaw.exe
20+
-vmargs
21+
-Xms128m
22+
-Xmx1024m
23+
24+
- [#107 Failed to connect to Standalone V8 VM](https://github.com/Nodeclipse/nodeclipse-1/issues/107) even on JDK 1.6.0_30
25+
was solved by running `node --debug-brk app.js` first.
26+
Quote haroldjiang:
27+
28+
yes,the solution is to run node --debug-brk app.js first.
29+
30+
see also Debug page.
31+
1032
### Run Configuration
1133

1234
You can configure node and apps parameters workspace wide in `Preferences -> Nodeclipse`

0 commit comments

Comments
 (0)