In Internet Explorer 8 and earlier versions, you can use the error object to get the stack trace of a thrown exception. Here’s an example of how you can modify the code to log the stack trace: resolveWith: function( context, args ) { if ( !cancelled && !fired && !firing ) { firing = 1; … Read more
exception.getClass().getSimpleName(); Class#getSimpleName() NOTE: this will not work in case if your exception is an anonymous class (although I have personally never seen an anonymous exception in any production code)
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
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
You probably want DBMS_UTILITY.FORMAT_ERROR_BACKTRACE function SQL> ed Wrote file afiedt.buf 1 create or replace procedure p1 2 is 3 begin 4 raise_application_error( -20001, ‘Error 1’, true ); 5* end; SQL> / Procedure created. SQL> create or replace procedure p2 2 as 3 begin 4 null; 5 p1; 6 end; 7 / Procedure created. SQL> begin … Read more
Compile with -g and set environment variable OCAMLRUNPARAM=b
You can use a EnhancedPatternLayout in log4j to format your stacktraces. See http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/EnhancedPatternLayout.html, specifically the section about the “throwable” pattern in the pattern table. Note that support for the %throwable{n} support is rather new and requires at least log4j 1.2.16 (which is the latest at time of writing) For tracking purposes, this is the ticket … Read more
The error object, which would contain a “sanitized” stack trace, is now being passed in as the fifth parameter to onerror in Chrome. You can read about it here: https://code.google.com/p/chromium/issues/detail?id=147127 At the time of this writing it’s in Canary and should be pushed out to the stable Chrome release sometime later this month. If you’re … Read more
To get the line numbers in the StackTrace, you need to have the correct debug information (PDB files) alongside your dlls/exes. To generate the the debug information, set the option in Project Properties -> Build -> Advanced -> Debug Info: Setting it to full should suffice (see the Advanced Build Settings Dialog Box docs for … Read more
The MethodHandles class (as of Java 7) includes a Lookup class that, from a static context, can find and return the name of the current class. Consider the following example: import java.lang.invoke.MethodHandles; public class Main { private static final Class clazz = MethodHandles.lookup().lookupClass(); private static final String CLASSNAME = clazz.getSimpleName(); public static void main( String … Read more