I am trying to run Erlang compiler from Eclipse but it continuously shows nothing or Eclipse becomes not responding. According to one of these tutorials,
http://www.youtube.com/watch?v=lrkhIGzCr3Q
when I press the run button, tt must show me Erlang console window for me to interact with but my Ecllipse with Erlide does not show me anything and sometimes it become not responding. I have tried few possible solutions for the issues including
// including this in eclipse.ini -Derlide.runtime=/path/to/your/erlang/installation/directory
http://erlide.org/blog/2013/03/10/problems-at-first-start/
// Adding Erlang installation path to environment variables
http://myadventuresincoding.wordpress.com/2009/02/11/erlang-getting-started-and-using-eclipse/
// reinstalling erlide with new Eclipse copy
However, I still cannot run Erlang on Eclipse properly. I am happy to explain furthermore about the issue I am having and I hope to receive suggestions.
I solved it by doing a couple of things
1) reinstalling current Erlide plugin on Eclipse with http://erlide.org/update_nightly/
2) making sure go to
run -> run configuration -> runtimes
and set to "short name"
I hope this helps anyone. Good luck
Related
I change my Hard drive and so I made a fresh Eclipse Corrosion install but I kept my Rust projets. Problem is I get an error when I launch my prog in debug mode. It seems to work in run mode but I didn't test this that much.
Error is
An internal error occurred during: "Launching my_prog".
Cannot read the array length because "launchConfigEnv" is null
Important note : it seems to be link with the use of an input file (debug configuration/common/input file)
I try many things, many installs, new projects, many, many things but nothing works (and I cannot figure out what launchConfigEnv is).
Any help welcome...
Edit : I install 2019.12 Eclipse and it works fine. I will work a little with this version and try out more configuration to shrink the problem.
As a workaround, add a single environment variable to the launch configuration, as follows:
Once that is done, re-launch it and it should work.
Note that in order to get rust debugging working in Eclipse I installed MSYS2 and the following MSYS2 packages.
pacman -S mingw-w64-x86_64-gcc
pacman -S mingw-w64-x86_64-gdb
pacman -S man
I followed some instructions in the Rust Corrosion Trouble Shooting guide to get a working GDB.
Reference: https://github.com/eclipse/corrosion/blob/master/documentation/Troubleshooting.md#debugging-on-windows
The Rust debugger command needs to be changed to rust-dbg.cmd, as follows:
However, the PATH environment wasn't working for me, so in the rust-gdb.cmd script I added this near the top:
SET PATH=%PATH%;F:\msys64\mingw64\bin;F:\Data\.cargo\bin
(Adjust as-per your installation of MSYS2 and Cargo/Rustup)
After which Eclipse was able to start a debug session and stop at a breakpoint.
I've installed Eclipse Neon.3 on my windows 7 machine, after the install process has finished, the installer has an option to 'launch now', which I do and the IDE boots up and works as expected.
However when I close eclipse and then reopen it, I get a crash which prevents it from booting up (sorry for this being a picture, but there doesn't seem to be an easy way to copy the text):
The version I've installed is Release 4.6.3, and the build ID is 20170314. I've installed and removed it 3 times and observed the same behaviour each time. I've tried doing a reset between boots and installs. I've also tried inspecting my environment variables, which look like this:
JAVA_HOME:C:\Program Files\Java\jdk1.8.0_91
PATH: %PATH%;%JAVA_HOME%\jre\bin
Is this a known issue, or do I have something wrong in my setup? Prior to this I discovered 4 versions of the jre/jdk on my machine, and two versions of eclipse. I think I have correctly removed all but the one referenced from my java home, and I entirely removed eclipse and downloaded the latest version (neon.3).
I've fixed the issue, and whilst I'm still not entirely sure why it was a problem, here is how I fixed it.
I opened a terminal and ran 'java -version' (I should have done this first). It was failing to find java.exe, despite the bin folder being on the path. Running this revealed that it was actually calling a shortcut to java.exe found in 'c /programdata/oracle/java/javapath/' which pointed to a now non existent version of java.
So long story short, if you have a similar problem, check if you have shortcuts in the folder 'c /programdata/oracle/java/javapath/java.exe' and ensure they point to the correct program.
A few days ago, Eclipse for C/C++ (Helios) stopped running my programs. They can be compiled with MinGW without displaying any errors. However, when the programs are run, Eclipse always get stuck at "Launching Delegate" at 70%. No matter how long I wait, the program never starts. The same happens when I try to run the program from the command line; no matter how simple the program, the command line just does nothing, as if it is waiting for the program to start.
I believed that this was just an issue with my Eclipse workspace, so I created a new workspace and tested a Hello World application, but it failed too. I reverted to an older version of Eclipse (Indigo), and a 32-bit version, but these had the same error. I even installed a different IDE, Netbeans, but it too never runs any programs. So, clearly, it's not just Eclipse. I tried reinstalling MinGW, but this also didn't help.
I have tried everything I can possibly think of. I could only find one other person with the same problem online, and theirs was never answered. Can anyone help me out with this strange issue?
I had the same problem. Always stuck at 70%. However, it turned out that somehow it can be fixed by disabling my anti-virus program, when I want to run a C/C++ program. Which I find to be quite strange.
I hope it helps.
I have a strange problem when using Pydev on my work machine (others at work have the same issue). It does not occur when I do this at home, which makes me think it's something to do with the environment at work. We are running Windows 7.
I am using Pydev 3.9.2 but the same thing happens with earlier versions. It occurs with all versions of Eclipse after 3.7. The problem is this. When I create a jython console (the one running in the Eclipse VM), the error output doesn't work. If I type an invalid python command, there is no output on the console. It just appears that the command worked. If I type a command such as "print 100", the output prints as you would expect.
The second problem is that if I hit the red square which is supposed to remove the console window, Eclipse crashes. There are no errors or any indication of what is going wrong.
I have tried different versons of eclipse, different versions of Pydev, different machines and it doesnt make any difference.
Has anyone seen this? I've tried everything I can think of to debug this issue so any help is appreciated.
thanks,
brian
Unfortunately those quirks are expected...
The internal console in Eclipse is mostly a developers SDK for experimenting with Eclipse itself and is not meant as a general shell (you should configure an interpreter and use it for that).
I don't have plans on improving on that situation (there's already a multi-year backlog on PyDev and this isn't really critical), but if you'd be willing to spend some time and fix those issues, pull requests would be definitely welcome -- see: http://pydev.org/manual.html for details on getting the code and setting up the environment.
Every time I try to run a .py module it just opens in Firefox.
I'm running Aptana in OS X 10.6
If you installed and configured PyDev, it should work.
Make sure you use the correct "Run" command. Prefer "Run as Python module", avoid "Run on Server".
If that doesn't help, edit your question and give an exact example what you do (which menus/buttons you click, etc).
See: http://pydev.org/manual_101_run.html for details on running a Python module (make sure you read the whole getting started: http://pydev.org/manual_101_root.html which should help you in getting your environment setup and gives some tips to properly use PyDev).
I used a same workspace for both python and java , and met the same problem.
If I change a new workspace, the Run As works. So i think there is something wrong with workspace settings.