As far as I know, the only way to make the stack trace available to your own code is via the getStackTrace() method in the Error class, just like you’re already doing. In response to the example in your question, though, I would mention that you don’t actually have to throw the Error — you … Read more
It’s possible to catch a Throwable object in Java without a stack trace: Throwable(String message, Throwable cause, boolean enableSuppression,boolean writableStackTrace) Constructs a new throwable with the specified detail message, cause, suppression enabled or disabled, and writable stack trace enabled or disabled. public Throwable fillInStackTrace() Fills in the execution stack trace. This method records within this … Read more
When you see ‘…113 more’, that means that the remaining lines of the ’caused by’ exception are identical to the remaining lines from that point on of the parent exception. For example, you’ll have com.something.XyzException at … at … at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242) at … <the other 113 lines are here>… Caused by: <the above>. The two … Read more
here is an explanation of the ’caused by’ and ‘… n more’ lines in the printed trace. see also the JavaDoc for printStackTrace. you might not have any work to do. Note the presence of lines containing the characters “…”. These lines indicate that the remainder of the stack trace for this exception matches the … Read more
While debugging, Go to Debug -> Windows -> Call Stack
With the JVM flag -XX:-OmitStackTraceInFastThrow you can disable the performance optimization of the JVM for this use case. IF this parameter is given, which disables the flag, the stacktrace will be available. For more information please have a look at the following release notes: “The compiler in the server VM now provides correct stack backtraces … Read more
You pass the exception directly to the logger, e.g. try { … } catch (Exception e) { log.error( “failed!”, e ); } It’s up to log4j to render the stack trace.
0 MyApp 0x000833a3 +[TFCrashHandler backtrace] + 26 Crash was generated from +[TFCrashHandler backtrace] + 26; from whatever instruction fell at that symbol location + 26 bytes. If that is really the bottom of your stack trace and it crashed there, then the TCrashHandler is obscuring the real crash. The real crash looks to be a … Read more
Throwing twice in the same method is probably a special case – I’ve not been able to create a stack trace where different lines in the same method follow each other. As the word says, a “stack trace” shows you the stack frames that an exception traversed. And there is only one stack frame per … Read more
I don’t believe this is possible using the standard Java API. What you could do is to use AspectJ, place a point-cut at the calling method, save the arguments, place a point-cut at the called method and pass on the arguments. Another option (slightly more advanced) is to use a custom, bytecode-rewriting, class loader that … Read more