BTW, displayName, even though is not standard, is not Chrome proprietary. Firebug supports it. Supposedly Safari should be supporting it as well: https://bugs.webkit.org/show_bug.cgi?id=25171
If it is not fixed by next release, we should provide at least an opt-out for incremental name obfuscation (which is only enabled on the trunk, not 2.7). On Mon, Dec 8, 2014 at 5:11 PM, Goktug Gokdogan <[email protected]> wrote: > We are using pretty naming in 2.7 so even using Safari he should get > non-obfuscated names by default. If I'm not missing anything; if he is > getting obfuscated names either he is using trunk (not 2.7) or incremental > is not enabled. > > On Mon, Dec 8, 2014 at 3:45 PM, 'Ray Cromwell' via GWT Contributors < > [email protected]> wrote: > >> He said he's not using Chrome, he's using Safari, which I don't think >> respects the displayName feature. We can't rely on cross-browser >> debugging supporting a client-side Chrome proprietary feature. IDEs >> and SDM need to support source-map/symbolmap based log deobfuscation. >> >> On Mon, Dec 8, 2014 at 1:40 PM, 'Goktug Gokdogan' via GWT Contributors >> <[email protected]> wrote: >> > >> > >> > On Mon, Dec 8, 2014 at 1:00 PM, confile < >> [email protected]> >> > wrote: >> >> >> >> I use GWT-PhoneGap on an iPhone5 and Super Dev Mode. SDM works file. I >> use >> >> the Safari console for logging. >> >> >> > >> > The problem is you shouldn't be seeing obfuscated method names in GWT >> 2.7 >> > SDM as incremental compiler uses pretty names. You should see "at >> > Unknown.somethingMeaningfulHere$(Unknown Source)" instead of "at >> > Unknown.gPc_g$(Unknown Source)" without stacktrace deobfuscation. >> > >> >> It would be great if you could provide an example of how >> >> StackTraceDeobfuscation worked. I see there is a lack in the >> documentation. >> >> >> >> Michael >> >> >> >> >> >> Am Montag, 8. Dezember 2014 21:28:56 UTC+1 schrieb Goktug Gokdogan: >> >>> >> >>> 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? >> >>> >> >>> On Mon, Dec 8, 2014 at 10:25 AM, Jens <[email protected]> wrote: >> >>>>> >> >>>>> I use it like this: >> >>>>> >> >>>>> GWT.setUncaughtExceptionHandler(new >> >>>>> SuperDevModeUncaughtExceptionHandler()); >> >>>> >> >>>> Then just throw an exception somewhere in your app that you do not >> catch >> >>>> yourself. The handler does not fix your java.util.logging.Logger or >> >>>> GWT.log() calls. >> >>>> >> >>>> But as you are using Safari you might not get any benefit of it >> anyways. >> >>>> In that case, as already said, your only chance is to use remote >> logging and >> >>>> use StackTraceDeobfuscator on a server to make the exception >> readable. >> >>>> >> >>>> -- 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/e0ebec63-bd88-4f12-b9f3-bbb59fbe4763%40googlegroups.com >> . >> >>>> >> >>>> For more options, visit https://groups.google.com/d/optout. >> >>> >> >>> >> >> -- >> >> 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/6a0c1571-da4a-4ba5-8ff2-77a68c06e517%40googlegroups.com >> . >> >> >> >> For more options, visit https://groups.google.com/d/optout. >> > >> > >> > -- >> > 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/CAN%3DyUA10f-igQmV3zcSgH71S25AKhCX0GFs0LTVBd%3DOb%2BYjGNw%40mail.gmail.com >> . >> > >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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/CAPVRV7dUkJxbLxdDpP9wkeBmswqs4DcUob4PrtpOXG2aeuWwsw%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/CAN%3DyUA0i%2B-wnq-s2SNzfKb3H65py2H5FJOEjMZd-mFefnhuhKA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
