Eclipse 4.4 suddenly stopped printing stack traces to console

Question

Ever since I've begun using eclipse, whenever an exception occured I'd get a message and a stack trace in the console, no matter if I caught the exception or not.

Now however, all of a sudden the only thing that is printed to the console is the class of the exception and a message if there is one. I haven't changed any settings manually but I did install Grep Console for eclipse.

Can I get stack traces back somehow without having to reinstall eclipse? I've looked around the preferences for compiler and debugger but haven't found anything which even remotely seems like it manipulates console stack traces.

Here's how exceptions are presented now. It's really difficult to do any sort of debugging without a stack trace now:

Answer 1

I know this post is old, but you have to add

-XX:-OmitStackTraceInFastThrow

as a JVM-Option

Answer 2

I've checked everything: call hierarchy for any hidden try-catch blocks, logger configuration, eclipse run configurations but found nothing. So as a last resort I reinstalled Eclipse and JDK for good measure, and now I've gotten full stack traces back. I have no idea what was the cause but now everything is back to normal.

Answer 3

Eclipse just collects what your program (or the JVM if an exception is not caught) prints to System.out and System.err.

Hence it is not Eclipse but the logging environment in your own program that has changed. Based on the output it appears to me that you have been experimenting with the logging pattern in logback (or log4j 1). If the %ex conversion word is not present in the pattern, stack traces are not printed.

See http://logback.qos.ch/manual/layouts.html#conversionWord for the full list of conversion words.

Answer 4

Go to : Window -> Prefenrences Find : Grep Console(search) Disable : Grep Console