> > The stack traces that are logged as escaped exceptions (with missing > causes) and the ones that are logged by Logger (without inheriting > c.g.gwt.logging) will be deobfuscated by Chrome dev tools (if haven't > already fixed in Dev channel). > Being said that, I don't understand why you are not seeing pretty names > for your methods. Are you not using incremental? >
Not sure who you mean since you answered my mail but for me it is pretty clear: 1.) deobfuscation only works in Chrome 40 (currently beta) and only if you do not inherit Logging/LoggingDisabled but still use Logger to log the exception. AFAICT it doesn't work at all using GWT.log() because currently SuperDevModeLogger only builds a plain String of the Java exception for now. People might use other browsers, like confile/Michael who develops on his iPhone using Safari. 2.) There seem to be a bug in LogImpl.gwt.xml because Logger output does not appear in SuperDevMode if you do not inherit Logging.gwt.xml. At least I wasn't able to make it work in a small app of mine (maybe the superdevmode property is always "off" in incremental mode?) 3.) If you inherit Logging to make Logger work you automatically loose deobfuscated stack traces because the Logger is now configured differently. Can't we streamline it so it always works (at least in Chrome 40) no matter what is inherited and what is not inherited? -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/b2c274dc-0c28-4e76-befd-7ee17fd3a26a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
