I always deploy a version compiled with emulated stack traces alongside the regular version so that if a problem can be replicated, I can get a proper stack trace.
But I still share your pain. Trying to work out which line of obfuscated JavaScript could possibly have given a null pointer exception can be quite tedious. I'd be (happily) surprised if it's possible to improve stack traces or error messages without slowing things down. Paul On Mon, 5 Nov 2018, 18:59 brad <[email protected] wrote: > Hi, > > Two issues that often frustrate me with GWT deobfuscated stack traces: > a) The stack trace is deobfuscated, but the error message is not, so you > get something like "com.google.gwt.core.client.JavaScriptException: > (TypeError) : Cannot read property 'a' of undefined". > b) The stack trace refers to methods headers, rather than specific lines. > > In many cases, neither of these is a big deal, but if the message is > obscure and the method in question is long it can make debugging difficult. > Is there anything that can be done to work around this (compiler > properties, etc.). This is particularly for debugging a deployed > application, not locally using super dev mode. > > Thanks, > Brad > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
