Eclipse Juno- Suddenly “cannot run program 'make' : unknow reason” - eclipse

I'm using Eclipse JUNO for developing C applications. It runs on Ubuntu 12.04 inside a 3-CPU, 1GiB RAM virtual machine.
Everything works perfectly, but sometimes, I cannot build my application any more and the following error occurs:"cannot run program make; unknown reason".
Any idea on how to fix this?

Apparently this error is due to low memory conditions. It mostly occurs after searching in files within Eclipse (a search that returns a large result set). If the error occurs again:
Re-start Eclipse and try again
If it does not fix the problem, you need to completely reboot the OS

Related

Eclipse always exit when used in a virtual machine

I use ubuntu16.04 in VMware for learning Hadoop. The eclipse is Eclipse IDE for Java Developers at 2020.03 for linux_64.
And when use eclipse to write some java code, the IDE usually exits by itself without any error. And the eclipse is too slow when I use it. I guess that whether the memory is not enough for using IDE. But I found the memory is free when I check it. I allocated 2G of memory for ubuntu16.04.
And I search for this problem on web. I found many people believe the problem is eclipse caused. So they come up with a way to edit eclipse.ini.
-Dorg.eclipse.swt.browser.DefaultType=mozilla
Add this command to the last line of eclipse.ini.
Unfortunately, it doesn't work. So Do u know why? Should I allocate more memory for VMware?

Valgrind in Eclipse Cannot Connect to X Server

I am using Valgrind to debug an OpenCV application. My application often stops with Segmentation Fault error. I thought this is related to memory, so I debug it using Valgrind in Eclipse. Unfortunately, when I run the valgrind profile in Eclipse, it returns : cannot connect to X server and valgrind stops executing my application.
According to this post, I have set DISPLAY variable to 0.0, but same behavior still happened.
I also tried installing xorg and openbox, but still nothing happened.
The application runs until before I called "cvNamedWindow(WINDOW_TITLE, CV_WINDOW_AUTOSIZE);". On executing the line, Valgrind outputs : cannot connect to X server and then stops.
Based on my previous experience with Valgrind, I expect it will execute the application, and exits when memory problem happened/application terminated, because that is what happened if I run the application normally (Segmentation Fault). Also, thats how I debug multithreading in in an application, previously.
Any help is appreciated. Thanks!
I tried running the application with valgrind, root privilege in terminal:
`sudo valgrind --tool=memcheck <path-to-application>/myapp`
and it works. Seems like the Eclipse plugin do not have root access to X server/display. The problem is solved

eclipse remote project with sftp - dltk indexing results in 'no more sessions' error

I am running a virtualbox with debian installed as local webserver. I am working with eclipse directly on that virtual box with a remote project (RSE plugin). I am having the problem that eclipse starts the DLTK-indexer as soon as I open the project. On the debian machine, instantly my /var/log/auth.log is filling up with a endless list of:
sshd[4271]: error: no more sessions
In eclipse, the error log is filling up with (although using JRE 6):
org.eclipse.core.runtime.CoreException: Operation failed. File system input or output error: rse://xxx.xxx.xxx.xxx/path/to/file/being/indexed
org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
While indexing is done, I am not able to save any file I am working on, as all ssh-sessions are already used on the server.
It seems that the indexing process tries to open a new connection for every file it´s indexing.
When indexing is finished, everything works normal again, I can save files etc.
I would appreciate the indexer to complete its work, but as code completion does not work afterwards, eclipse was not able to do the indexing.
One solution would be to disable the indexing, but this is not the purpose of an IDE, code completion is one of the few reasons for me to still use an IDE (at least for large projects).
Any ideas on how to make indexing work and get rid of the ssh-errors would be great!
Futher system information:
Host-System: Windows 7 Prof. 64bit
Guest-System (virtualbox): Debian Lenny with sftp subsystem enabled
Eclipse: Indigo with Zend PDT and RSE (already running with Java 6 JRE 1.6.0_45)
Thanks for your help!
David
I was able to fix this issue by doing two things:
set up ssh to use multiplexing (see http://en.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexing) in the virtual machine
Upgrade eclipse to Kepler 64Bit release (much faster and more stable in Windows 7) with manual installation of PDT feature (using Zend PDT is a waste of time)
This also works with Java7!
Now I have completely indexed projects and can use code-completion!

Eclipse debugger stops working randomly

I have been working on a project that requires rigorous debugging at each step and I notice that my debugger just randomly stops working from time to time and does not respond to any of the breakpoints.
I tried restarting eclipse and unplugging my device over and over. Any particular reason this might be happening? Its extremely frustrating and I couldn't think of a better place to post this query.
Many a thanks in advance!
I know this is an old question. But I had that eclipse suddenly stopped working, i.e. died before even executing one line. I restarted VM and eclipse multiple time. Then I stumbled here. Thank you, it got my mind thinking.
For all major issues with eclipse, not loading, freezing or debugger fuck up (that is not because of your code :D ). Try the following line:
./eclipse -clean -clearPersistedState -refresh
First I would make sure your eclipse is not running out of heap space memory. If necessary increase the heap memory using the -mx Java command line flag. Running out of memory can cause various instability problems such as the one you describe.
-xms is the start memory (at the VM start), -xmx is the maximum memory for the VM
eclipse.ini : the memory for the VM running eclipse
jre setting : the memory for java programs run from eclipse
catalina.sh : the memory for your tomcat server

Eclipse does not find Valgrind

I installed Valgrind on SUSE Linux SLES 11SP2 under my home directory and added it to the path. I then installed eclipse Juno for C/C++ Service Release 2 Build id: 20130225-0426 and installed the Valgrind plugin.
When I try to create a profile configuration with Valgrind I get an error message:
"[Valgrind Options]: Couldn't determine version of Valgrind", and though it allows me to make the configuration it prevents me from proceeding by greying out all buttons except for the close button.
I know I am missing something trivial like defining the location of the Valgrind executable in eclipse, but I was unable to find it, not in the project properties nor in the window preferences.
I will appreciate your help.
Ok, I figured it out.
I moved the Valgrind installation to a new shared location, and tried it out with a new computer (same architecture).
It did not affect the original computer I installed it on, but Valgrind had a problem with the new one, as indicated in the README (and I meanwhile forgot):
“Important! Do not move the valgrind installation into a place different from that specified by --prefix at build time. This will cause things to break in subtle ways, mostly when Valgrind handles fork/exec calls.”.
This caused Valgrind to break when run standalone with the message:
“valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No such file or directory”,
however when running Valgrind from eclipse it probably translated it to the message:
"[Valgrind Options]: Couldn't determine version of Valgrind".
In short: Do not move the Valgrind installation but re-install it. And this message from eclipse indicates that something bad happened with the installed Valgrind and not that it cannot find it.
I am getting the same error but its not caused by the explanation you have given.
You can get this error if you are using valgrind on mac os x because valgrind is usually not installed in the directory eclipse is looking for. In order to fix the issue on mac, you need to make a symbolic link to the valgrind location by
typing ln -s valgrind_location /usr/bin/valgrind. Note this differs from what are in the directions on eclipse's site http://wiki.eclipse.org/Linux_Tools_Project/Valgrind/User_Guide. For some reason they have the call backwards on their site. Once I made this correction valgrind worked correctly from within Eclipse.
So on macs at least the error that it can't determine the version of valgrind at least matches up with eclipse not being able to find the file.