Tracking down causes of exceptions in Eclipse

NOTE: I found this in a Blog somewhere.. Thanks and due credits to the author, who ever he/she is :)


If you like me is getting tired of seeing "Unhandled event loop exception, Reason: someexception" and no stacktrace in Eclipse then try the following:

Create a file e.g. .eclipseoptions with the following contents:

# Turn on debugging for the org.eclipse.ui plugin.
# Show a dialog with details button when an internal error occur.
# Print exception stacktrace to console

and then run eclipse with -debug .eclipseoptions and you will get the full stacktrace
as normal in the log but also on the console (clickable) and in a dialog when the exception occurs - no need to go looking in the log what just happend.

p.s. try to include the following too:

# Enable heap status monitoring

Gives you a nice hint about memory you are "utilizing"



blogsurfer said…
Hi, I was just blog surfing and found you! If you are interested, go see my strange ebay auctions site. It isn't anything special but you may still find something to entertain you.

Popular posts from this blog

10 years on, #Blockchain is ready for Business use... thanks to the #Hyperledger project!

HTML5+h.264+WebSockets == Begining of the end for Flash?