Two issues that often frustrate me with GWT deobfuscated stack traces:
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.
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@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Post a Comment