Eclipse(CDT) crashes on Ctrl-clicking in Ubuntu - eclipse

I am relatively new to Eclipse and I was trying to browse thru an existing C++ project I created. However every time I try & use ctrl-click on say a function invocation - instead of taking me to the declaration (or is it the definition?), Eclipse crashes.
I am running Eclipse 3.2 on 64-bit Ubuntu. I tried setting -XX:-UseCompressedOops in ~/.eclipse/eclipserc as was suggested here, but that resulted in:
/home/dp/.eclipse/eclipserc: line 1: -XX:-UseCompressedOops: command not found
Any suggestions would be greatly appreciated! TIA.
Note: Btw, I didn't find an eclipserc file in ~/.eclipse, so I just created a new one with just the one line in it(being -XX:-UseCompressedOops).

I upgraded to Eclipse 3.7.0 and this problem was resolved. Thanks for the helpful suggestions, though.

Related

Getting "Error: Failed to connect to OmniSharp"

I'm trying to get VSCode working with my Unity projects, and every time I select the Project icon (the little fire at the bottom) I get the following error:
Error: Failed to connect to OmniSharp
Is anyone else getting this?
You need to download the most recent version of "mono". Open up terminal and pass in brew install mono. Then "Pick a project" and select the ..-csharp.sln file and you should be up and running.
Ok, made some progress and gotten a few Unity projects working. It seems that you need some prerequisites installed, a clean up of your Unity project folder, and possibly some hand editing of your .sln and .csproj files.
I posted a (possibly) better answer over on Reddit. Hope that's not breaking stack etiquitte.
http://www.reddit.com/r/Unity3D/comments/34d6gc/visual_studio_for_mac_help_us_vote_for_unity/
i get this on windows when my project directory has a space in it
i removed the space and removed the error
i expect it will be fixed soom
I have a completely different answer: it's the runtime that VSCode is using. It doesn't match up with what it thinks it needs. I have to remember that we're still in beta and that things are changing rapidly. I had my dnvm running beta 7, but VSCode (and OmniSharp, by extension) is looking for beta 6, so it was failing. I updated my runtime using this this post as a clue. Now I have VSCode 0.7.0 using the beta 6 runtime. I have no idea how to tell what it's looking for...I just guessed based on when they were both released. HTH

Eclipse Build Error "A class file was not written. The project may be inconsistent, if so try refreshing this project and building it"

I have been struggling with a very weird issue that has suddenly popped up on the latest version of Eclipse Classic (4.2.2).
Everytime I try creating or refactoring a class or subclass in any of my projects (all Java) in my Eclipse workspace I get an error at the very top of my class that says
A class file was not written. The project may be inconsistent, if so try refreshing this project and building it
Again, this happens when I create new classes. And even when I rename current classes, then undo the renaming, its totally fine, but changing a single character in the name causes this error to happen for that specific class.
I have Auto Build on, and I tried multiple times to clean and refresh every project as well as restart Eclipse entirely.
I have literally no idea how to even start figuring out how to fix this. The solutions i've found through search didn't help, so i'm hoping I might find any clues here.
I had the same problem and here's how I solved it in the end:
It turned out that the disc space on the drive where workspace resides was full.
Silly mistake but worth checking.
In my case, this was caused by the fact that the build output directories were owned by a different user, and Eclipse could not write into them.
I had the same issues, the following worked for me:
Right click eclipse then running "as an Administrator"
Click Project > Clean.
Clean your workspace by starting eclipse from the command line with the -clean argument :
eclipse -clean
See also How to run eclipse in clean mode? and what happens if we do so?
I solved this problem by running Eclipse as root.
I had the same issue on Mac OS X. I had a maven project.
Try running the following command on Terminal. This looks like an access issue.
sudo mvn clean
Provide password for admin user.
Then open Eclipse and refresh your project.
We are using Eclipse here too and have to handle a workspace with more than 200 plug-ins. Every now and then people have similar problems with their workspace and inconsistencies reported in a weird way by Eclipse.
What people here usually do is (next step only in case previous step didn't help):
- trying to ContextMenu->Team->Clean/Refresh the whole workspace
- creating a new workspace and check out all necessary files from the repository
- reinstalling Eclipse to a new directory
From my experience after using the Eclipse IDE on a daily basis for many years, it doesn't make very much sense to waste too much time with these issues, unless they aren't solved by one of the steps above. It takes too much time to struggle with these things, while starting from scratch is done in an hour or less (and usually fixes the issue).
If your Eclipse still behaves strangely it might make sense to go through your installed plug-ins. Not all external plug-ins follow the Eclipse guidelines and can seriously harm the performance and operational consistency of your Eclipse installation (E.g. Sonar Plug-in, Toad Plug-in, ...)
In my case this kind of error caused due to disk space got full and it got resolved by just freeing disk space where eclipse have been installed.
That is c/d/e drivers.
I come up with the same error, and in my case, this is because the permission of the project/bin directory is not recursively 775
I fixed it by:
Remove the project/bin directory: sudo rm -rf project/bin
Switch to Eclipse, rebuild the project: Project->Clean...
Then no errors.
Try to launch Eclipse as Administrator.
In my case such error was caused by a question mark in a quoted method name (I use geb+spock combination for automated testing).
So this method name will throw an error "Do you want something?"()
And this will not "Do you want something"()
It may not be the best response but to fix it, I've just delete the error marker.
Had the same issue. but cleaning the project and restart eclipse didn't help and disk space was not the issue. Solved the issue by copy the code to notepad(just to not lose it) and then delete the class, recreate it and paste the code back in again.
I solved it changed the owner of the project files. I changed from root(old owner) to user my current(user that i use with eclipse).
Just changed and saved java file to recompile the class. Then error disappeared.
I was try run
Project->Clean...
And Rebuild. My problem was resolved
For linux (Debia) and working on Spring boot project (maven):
$ sudo mvn clean
Then open Eclipse and File -> Refresh.
I had same issue, it is something similar but this post didn't help in my case. I have many inner classes which is causing the compiler to create class names with all inner class names together that is creating class name more than 255 character file limit on NTFS! read it in some other blog. I thought it will be helpful to post here.
Ex : classA$InnerClassB$......InncerClassZ.class in target folder it won't generate the class if it exceeds this limit. Try renaming your inner class name shortened. In my case i have to add InnerclassZ as its exceeding its not generating class and Eclipse complaining.
A class file was not written. The project may be inconsistent, if so try refreshing....
I shortened InnerClassZ to IClassZ fixed the issue.
I had the same issue and it got fixed by running eclipse in administrator mode
Eclipse Shortcut-->Right click-->More-->Run as Administrator
I've been throught that error once when I used wsdl2java to extract java classes from a wsdl, it turns out that all classes were created in the same "class", causing end classes with long names (error - File name too long). When I organized and rename some classes the error disappeared.
I had this issue. I did the following, it resolved.
Open Eclipse in Administrator mode; Right click on eclipse.exe "Run as administrator"
Clean all projects.
#Denny's answer put me on the right track, though in my case it was the target directory. I deleted it for some reason and something automatically recreated with owner root. Changing the directory owner was not enough as it contained files that were also owned by root. So make sure to really remove the complete content of the directory and to change the owner.
In my case current user didn't have access to this project dir
Before giving a try to the above solutions. Just cleaned the project and it worked.

Netbeans 7: JVM Creation Failed, which settting to change in netbeans.conf (windows)?

I was having an issue with JVM Creation Failed when executing Netbeans in Windows, and after looking around i found 2 parameters that can fix the issue.
But i am unsure which to use, both fix the problem...
Can anyone tell me the difference and advise which i should be changing..
-J-Xmx512m
or
-J-XX:MaxPermSize=128m
Thanks in advance.
Not exactly answer to your question, but might help too:
If you are running for example Win 7 64bit and 32bit Java JDK, try to install 64bit JDK, it helps many people.
Another one solution, is to delete created temporary folders, which contain the file splash.PNG (in NB folder in Doc and Settings folder).
And maybe this can help too, close any opened PDFs in Adobe Reader (version 9 probably). I get this error more often while running the built app from NB IDE and running some PDF triggers this problem.

Description error in Eclipse IDE for BlackBerry app generation

I am creating a HelloWorld program in Eclipse IDE for BlackBerry.
But I am getting following error :
Description Resource Path Location Type
InvalidRegex: Pattern value '([a-zA-Z_]{1,63}[\s-a-zA-Z_0-9.]{0,63}[;]?)*' is not a valid regular expression. The reported error was: ''-' is an invalid character range. Write '-'.' at column '{2}'. BlackBerry_App_Descriptor.xml /HelloWorld Unknown XML Problem
I tried uninstalling jdk 7.0 and instaling jdk 6.0 and trying, as suggested by few ppl.
But it didnt work for me. Can anyone please provide a solution for this.
Thanks in advance !
Can be fixed by switching Eclipse default JRE from 7 to 6.
in Window->Preferences->Java
Or you can try by deleting the BlackBerry_App_Descriptor.xml and then it got created again.
If that doesn't help
The problem is with Java 1.7, which the plugin doesn't currently support. You will need to use Java 1.6 32bit for development with the Eclipse plugin.
First uninstall jdk7. Then download and install jdk6.
Next time do some research before asking. The solution was rigth there. You will become a better programmer if you try and read before waiting for someone's answer

No autocompletion on Eclipse(Helios)

I'm having a problem with the autocomplete option in Eclipse (Helios).
I've already checked Windows->Preferences->PHP->Editor->Content Assist and everything seems to be correct there.
And when I do get completions when I write "self::" in any of my classes, but this is the only situation I get it.
For example..
"parent::"
or
"$this->"..
Don't work at all.. any ideas?
Btw, I'm working under Lunix, Ubuntu 10.10
Thanks in advance.
A few things to check:
1) .project file contains:
<nature>org.eclipse.php.core.PHPNature</nature>
2) .buildpath contains:
<buildpathentry kind="con" path="org.eclipse.php.core.LANGUAGE"/>
3) Right-click project and go to Configure -> Add PHP Support
4) Are you using a namespace in your code? If so, does completion work without a namespace i.e. in a global namespace
I can also see quite a few open issues in bugzilla related to code completion in PDT. Take a look.
Since it seems that yoy've already tried the basic solutions that are documented across the web (phpnature, add php support, buildpath, etc.) it's probably best to look at the logs and provide any error that occurs when you try to call auto-completion.
You can "tail" the log and check if anything appears when asking for an autocomplete (press Ctrl+Space after writing "$this->" inside a method of a class):
tail myWorkspace/.metadata/.log -f
The error that appears may be usefull for searching google or for including here for others to help!
Seems like updating Eclipse to Build id: 20100917-0705 solved this issue.
If you just upgrade eclipse you should rename/remove workspace/.metadata
some times there is compatibility issues...