I am very newbie to eclipse as well as the node.js is concerned. I have tried several basic programs in node.js.
Now my question is there are many articles explaining how to debug the node program in eclipse. I dnt get it working. I am on windows 7 32-bit machine and installed eclipse Indigo with node-eclipse plugin installed..
Please can any body help me how to start debugging with programs.
Disclaimer: I am very new to eclipse IDE, Node & this stackover flow as well, please help..
Debugging - Breakpoint, Trace, etc... via Eclipse debugger plug-in
for V8
How to Install:
Update Site : https://nodeclipse.github.io/updates/
Testing Site: http://www.tomotaro1065.com/nodeclipse/updates/
How to debug:
Open the JavaScript source files that you want to set breakpoints.
Double-click on the ruler at the left end of the line you want to set a breakpoint.
If you want to remove a breakpoint, double-click on the ruler again.
Select the main source file of Node Application on the Project Explorer, open the context menu by right-clicking, select the [Debug As]-[Node Application] menu.
For more, Please Check Nodeclipse & Using Eclipse as Node Applications Debugger
Happy debugging ;)
Related
I develop software on Eclipse Mars IDE, under MS Windows 10 OS, based on Java v7. And now I've got some configuration problems related to the IDE. What I want, is that to run into JDK source code from the IDE once I click on the 'step into' (or in other way). I've included the 'src.zip' on the path in the way provided by the IDE. Yet, when I attempt to run into the source code, the IDE says the 'source code not found'.
I want this feature in order to be able to debug some things related to my current app.
Regards
You need to set this through the Java->Installed JRE's found in Eclipse -> Window ->Preferences. See screen shot below.
I am running Eclipse Kepler 2 on Windows 7 with latest nodeclipse installed and nodejs
When I debug, I don't understand why i cannot enter into the console box to see the values of variable (like in pydev). This document tells me to use "Expression View". But is there a way to enter into interactive console of eclipse to get output with nodeclipse plugin?
Here is what is installed in my eclipse.
Also, I see that there is a separate interactive console (see image), but i can't seem to enter anything over there. Am i missing some plugins? I tried installing eclipse plugin - chromedevtools and nothing.
Nodeclipse is already shipped with chromedevtools (0.3.9 versus Google chromedevtools that were 0.3.8)
is there a way to enter into interactive console of eclipse to get output with nodeclipse plugin?
It should be tested and/or developed at https://github.com/nodeclipse/nodeclipse-1/
BTW: Hint Right-click on Perspective tabs panel and select Hide text. The toolbar panel will be more compact.
I just installed the Aptana Studio 3 plugin on my installation of Eclipse Juno, and attempted to use a portable install of Firefox to debug with, so that my general browsing install wouldn't get mucked up with a billion debugging features I don't need.
I set Eclipse's Window->Preferences->General->Web Browser to use this new portable install, but... it's still trying to launch my other install of Firefox. ("Please close down to complete installation" or whatever. I know the portable one isn't running.)
I just cannot get it to launch to the right browser. Firefox Portable is set up to allow multiple instances to be open, so I can get both my permanent install and my portable install to work at the same time, but Eclipse is trying to open the wrong installation.
I've tried restarting eclipse, closing Firefox , both internal/external web browser options on the web browser page, and even rebooting the whole computer. There are no other references to Firefox in the Eclipse settings that I can find.
... Help?
Apparently that particular setting only affects browsing in the integrated browser, not running and debugging web applications.
The setting that needs to be modified for running/debugging is in the run/debug configurations. Why that doesn't by default automatically use the default browser set in the preferences page is beyond me.
In order to get Eclipse/Aptana to open the correct browser when debugging and running web applications, do this:
In the Project Manager, r-click on the project and go to Run As -> Run Configurations... and under 'Web Browser' in the left pane, either edit the default one or add a new run configuration. I just replaced the standard 'Firefox - Internal Server' entry.
In the Web Browser field, either type in the full path to the browser executable (in my case FirefoxPortable.exe), or click 'Browse' and browse to the executable.
That should do it. and now it's doing what I would expect it to.
While trying to setup Debug Configuration to debug my php project on Eclipse Java IDE for Web Developers, Eclipse Juno. There is no option to select the index.php. This is confusing because it is not even showing any files from the current workspace. Attached snapshot will explain further.
This is not letting me run the debugger, any clues here would be helpful.
Thanks.
As Atlanto suggested
"It looks like you don't have any 'PHP Project' since this dialog will show php projects only."
Thats the correct answer, Eclipse checks out projects directly and it may not check them out as Php projects. Hence make sure when checking out projects from Subversive to chose the 2nd option Find/Checkout as and then checkout them as a New Project using the wizard so they are checked out under the Php perspective and then can show under debug configuration.
This is my first attempt at creating an Eclipse plug-in. I've created one, along with a feature and update site. I set the target platform as my local Eclipse installation. When I run/debug the plugin from within the development environment everything works fine.
Now, my colleague installed the plug-in from the update site that I hosted. When he starts using any of the functionality exposed by my plugin he gets runtime exceptions.
He sees null pointer exceptions which didn't occur when I ran my plug-in project from my development environment.
I have a wizard that's part of my plug-in. When he close it he gets a "Unhandled event loop exception", and the wizard doesn't close. I didn't have this issue when I was running/debugging my plugin in my development environment.
Now I'm confused as to why the same plug-in is behaving differently in the production environment, as against the dev environment and when I was debugging it from my IDE. The target platform in both cases is the same Eclipse version. What could be the reasons?
And how do I debug the plug-in in a production environment? Is there a remote debugging capability for debugging the plug-ins on the production environment?
Any suggestions would be really useful!
To remote debug your plug-in, first add debug arguments to your target Eclipse .ini file
-vmargs
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
before launching it.
Then open another Eclipse instance with a workspace containing your plug-in project.
Open Run > Debug Configurations..., select Remote Java Application and create a new configuration.
As Project, browse and select your plug-in project.
Also fill in your connection properties (host of target Eclipse and port 1044).
Launching the newly created debug configuration allows you to debug your plug-in the same way you debug locally.
Now I'm confused as to why the same plug-in is behaving differently in
the production environment, as against the dev environment and when I
was debugging it from my IDE. The target platform in both cases is the
same eclipse version. What could be the reasons?
This is a classic: Eclipse plugins and RCP applications do indeed behave differently between PDT (the Eclipse IDE) and the exported product.
In your case, a NullPointerException thrown from the exported version but not from Eclipse is 9 times out of 10 an image or other resource files (properties, etc.) that is loaded by your code but is not listed in the build.properties of your plugin.
Anyway, you'll need to check the logs to retrieve the stacktrace and hunt down its cause. Such logs could be found in your friend's workspace under le .metadata/.log file
From your development workspace as it stands now, use the "Debug As -> Eclipse Application" menu item to startup a test workspace. When it starts up, you'll have two workspaces running: the original development workspace and the new test workspace. You can set breakpoints in your plugin code in the development workspace and run your plugin in the test workspace.
When your plugin execution in the test workspace gets to one of your breakpoints, execution will pause and you can use the Debug view in your development workspace to look at variables, set more breakpoints or anything else you want to do to debuf your plugin.
See the Apache Wiki for Developing with Eclipse.
Under Windows 10 with Tomcat running as a windows service I started:
tomcat8.5\bin\Tomcat8w.exe
& added in the Java tab as the first entry in Java Options to enable remote debugging:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n