Re: Removing obfuscation from a stack trace.

2017-03-18 Thread sadhana muppavarapu
Flying-w, Were you able to figure out how u can deobfuscate beyond this. I am struggling with same issue. -- 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

Re: Removing obfuscation from a stack trace.

2013-04-10 Thread Flying-w
The symbolmaps are created in shark_sencha_prototype/symbolMaps, I can see them there. However any value I try to specify for param-namesymbolMaps/param-name still results in an obfuscated stack trace. I attached eclipse to Tomcat and whenever RemoteLoggingServiceImpl.logOnServer() is

Re: Removing obfuscation from a stack trace.

2013-04-10 Thread Jens
RemoteLoggingServiceImpl does not read any init parameters from your web.xml. You should do something like: public class MyRemoteLoggingService extends RemoteLoggingServiceImpl { @Override public void init() throws ServletException { super.init();

Removing obfuscation from a stack trace.

2013-04-09 Thread Flying-w
I've implemented server side logging of client side exceptions, by making the following changes in gwt.xml: set-property name=compiler.stackMode value=emulated / set-configuration-property name=compiler.emulatedStack.recordLineNumbers value=true / set-configuration-property

Re: Removing obfuscation from a stack trace.

2013-04-09 Thread Andrea Boscolo
Read the StackTraceDeobfuscator doc [1], you are either missing the -deploy dir argument for creating the symbolMaps, or it is not in the right place. [1] http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/logging/server/StackTraceDeobfuscator.html On Tuesday, April 9,