In the Eclipse settings under General->Error Reporting there is the option "Enable debug mode". But what does it do? When I search for "Eclipse debug mode" I obviously only get results on how to debug programs with Eclipse, not about this option. I guess it creates more detailed log files?
(Or maybe more general: Is there a detailed explanation of every Eclipse option (at least for core and the normal packs from the official download page) somewhere?)
Speaking as one of the committers from the Eclipse Automated Error Reporting Initiative (AERI), this option is there to help us, the developers of AERI, debug the error reporting itself.
Switching the General > Error Reporting > Enable debug mode option on causes every error that shows up in the Error Log to cause an “An Error Has Occurred” notification – even if the same error has already been reported from this Eclipse instance. Also, AERI explains how it reaches its decision whether to send the report via additional messages in the Error Log.
Unless you are contributing code to AERI or need the extra verbosity to send us a detailed bug report, you should leave that option switched off (the default).
Related to the tooltip "Disables recently seen filters and increases the logging output" i assume that this is for sending exceptions and other error to the eclipse-developer team directly.
In the same page you can adapt the error reporting configuration.
When you install eclipse you get ask whether you want to support eclipse in sending errors to them. If you do not agree, this preference page helps to get it to work later on.
Related
I am having problems with setting up the Eclipse IDE for editing source code of SmartHome on Windows 10. I have done everything as it is described in the Setting Up a Development Environment guide.
However everything works until I open up the workbench. At the first start the so called "setup tasks" will be performed automatically which takes about 5 min. After that I still got like 100 errors of 200 items and a bunch of warnings.
In the official guide they say this might be normal. After performing the "manual setup tasks" however (which can be found under "help" in the menu bar) most errors should be gone, which does not happen in my case. Even after rebuilding all of the loaded projects there are still errors and warnings remaining.
Has anybody had similar issues and maybe a solution for that problem?
I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log
I installed the Redmine-Mylyn-Connector in Eclipse and had our admin install the Mylyn-Plugin for Redmine. The connection to Server seems to work:
When I try to add a query, I receive a Server Error:. Unfortunately no more details are available.
What are potential reasons for this error, and how can I solve the problem?
There might be useful details in the Error Log. Open the Error Log view (Alt+Shift+Q then L, or use Window > Show View...). I would clear the log first (using the red X button in its toolbar), then reproduce the error. You should see error details in the Error Log which might point you to the source of the problem.
I am using REDHAWK 1.9. While doing the development of C++ component, the IDE gives the following popup errors. This happens on a regular basis. If developing a C++ component it happens multiple times a day.
'Update Monitor' has encountered a problem. An internal error occurred during: Update Monitor.
Another popup gives the following:
An out of memory error has occurred. Consult the 'Running the Eclipse' section of the readme file for information on preventing this kind of error in the future. You are recommended to exit the workbench. Subsequent errors may happen and may terminate the workbench without warning.
It looks like this may be related to Eclipse Bug #400073
Particularly, see Comment #25:
Boost libraries are used within REDHAWK components and devices, and the R1.9.0 IDE uses CDT version 8.1.2
That thread also lists a couple work arounds including:
"A workaround for me was decreasing the indexers absolute cache limits from 64MB to 32MB, though I don't know if this will work in general. You may find the settings at Window -> Preferences -> C/C++ -> Indexer" from Comment #23
You could also try adjusting additional preferences within the indexer page, "Index source files not included in the build" and "Index unused headers" could be unchecked. This can be done on a workspace level or a per project level.
As a last resort, you could try a new workspace or disabling the indexer entirely.
I am using Symfony (1.31) - with Propel ORM to build a website. I have recently moved from using a text editor, to Netbeans (6.8) as my dev environment.
Coming from a compiled language (C++) background, I am used to setting break points in code etc as part of debugging. Web development I have encountered (atleast with PHP), has been largely hit and miss - well debugging has been messy to say the least, using echo statements, logging stuff to file etc. Well I hear that it is possible to debug PHP (i.e. set breakpoints etc).
I have scoured the net for documentation to show how to set breakpoints (say in one of the MVC layesrs) so that when the relevant page(s) is opened via a browser, the breakpoint will get hit and I can step through the code (ideally, watching the program variables).
Is this possible using Symfony and Netbeans 6.8?.
There seems to be support for XDebug: http://netbeans.org/kb/docs/php/debugging.html
If you have specific questions about configuring XDebug: http://wiki.netbeans.org/HowToConfigureXDebug.
More useful articles on PHP development in NetBeans: http://netbeans.org/kb/trails/php.html.
Hope that helps.
UPDATE: Just installed NetBeans 6.8 and ran through the configuration and was able to get breakpoints to work successfully with XDebug. NetBeans' integration with Symfony is pretty slick too, +1 to question for getting me to check this out.
Here is what has helped me debug my Symfony apps:
Enable logging and the web debug toolbar via apps/appname/config/settings.yml. Note: Any changes will require clearing the cache.
dev:
.settings:
web_debug: true
logging_enabled: true
Use var_dump() or print_r() with pre tags to dump data from anywhere. Adding exit; will allow you to dump variables from the controller or anywhere else.
echo '<pre>';
vardump($something);
echo '</pre>';
exit;
Enable logging and log messages. You can access the logger anywhere as well, but make sure you enable logging for your environment:
sfContext::getInstance()->getLogger()->info($message);
I've used Gubed with Quanta+ as a stepping debugger with PHP, don't know if you can get that to work with Netbeans but I thought it was more hassle that it was worth. I found that I could for(i=0;i<~6;i++){dump stuff to screen/log; make changes; reload;} and solve an issue in less time than it took me to step through it once with the debugger.
Xdebug is a very useful PHP extension which features a remote debugger with support for some editors, though Neatbeans isn't listed. I've not used the remote debugging element of Xdebug (see above) but the profiling, code coverage and - in particular - improved browser error messages I find helpful.
Generally with Symfony I find I can get most of what I need from stack traces or by dropping items into the logger and picking them up with either the debug toolbar or firesymfony.
Netbeans 7+ has trouble with xdebug breakpoints in the model/action. You have to use the manual function to set breakpoints.
xdebug_break();