Re: Deobfuscated stack trace message and line-specific stack traces
Thanks again Thomas.
net.ltgt.gwt.maven
gwt-maven-plugin
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/${project.build.finalName}/WEB-INF/deploy
On Tuesday 27 February 2024 at 4:06:12 am UTC+11 Thomas Broyer wrote:
> On Monday, February 26, 2024 at 11:56:45 AM UTC+1 ma...@craig-mitchell.com
> wrote:
>
> Thanks Thomas, now working great!
>
> For anyone coming from the Eclipse GWT plugin, you can do this to keep it
> consistant with how it used to work:
>
> In your client pom. Add the like this:
>
>
>
> net.ltgt.gwt.maven
> gwt-maven-plugin
>
> com.mycompany.mywebapp.App
> mywebapp
> >${project.build.directory}/mywebapp-client-HEAD-SNAPSHOT/WEB-INF/deploy deploy>
>
>
> nit: use ${project.build.finalName} rather than hard-coding the
> "mywebapp-client-HEAD-SNAPSHOT"
>
> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#webappDirectory
>
>
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/c3eddfb9-5590-4be4-9db5-a4ff22cd4e61n%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
On Monday, February 26, 2024 at 11:56:45 AM UTC+1 ma...@craig-mitchell.com
wrote:
Thanks Thomas, now working great!
For anyone coming from the Eclipse GWT plugin, you can do this to keep it
consistant with how it used to work:
In your client pom. Add the like this:
net.ltgt.gwt.maven
gwt-maven-plugin
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/mywebapp-client-HEAD-SNAPSHOT/WEB-INF/deploy
nit: use ${project.build.finalName} rather than hard-coding the
"mywebapp-client-HEAD-SNAPSHOT"
https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#webappDirectory
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/f57dfe88-40b6-4b91-af17-30148cda2d1fn%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Thanks Thomas, now working great!
For anyone coming from the Eclipse GWT plugin, you can do this to keep it
consistant with how it used to work:
In your client pom. Add the like this:
net.ltgt.gwt.maven
gwt-maven-plugin
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/mywebapp-client-HEAD-SNAPSHOT/WEB-INF/deploy
And then instead of reading the symbol maps directly like this:
String path = config.getServletContext().getRealPath(
"/WEB-INF/deploy//symbolMaps/");
StackTraceDeobfuscator deobfuscator = StackTraceDeobfuscator.
fromFileSystem(path);
You now read them from inside the war like this:
StackTraceDeobfuscator deobfuscator = StackTraceDeobfuscator.fromResource(
"/WEB-INF/deploy//symbolMaps/");
Cheers.
On Monday 26 February 2024 at 8:03:27 am UTC+11 Thomas Broyer wrote:
> On Sunday, February 25, 2024 at 12:34:44 AM UTC+1 ma...@craig-mitchell.com
> wrote:
>
> Sorry, I do see them in
> mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps
>
> How do I get them from there, into the war?
>
>
> Configure to somewhere inside the (preferably
> inside WEB-INF so they won't be served)
> https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#deploy
>
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/6ae923cb-f73f-41f6-bbd8-67879122e8cfn%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
On Sunday, February 25, 2024 at 12:34:44 AM UTC+1 ma...@craig-mitchell.com wrote: Sorry, I do see them in mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps How do I get them from there, into the war? Configure to somewhere inside the (preferably inside WEB-INF so they won't be served) https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#deploy -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/13cdf61a-f204-4b71-a7f6-312a77760740n%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Sorry, I do see them in mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps How do I get them from there, into the war? On Sunday 25 February 2024 at 10:30:14 am UTC+11 Craig Mitchell wrote: > Hi George, > > What I did was: > >1. Run https://github.com/tbroyer/gwt-maven-archetypes to generate the >sample app. >2. Modify module.gwt.xml to have: value="native" /> >3. Run mvn clean package. > > Then when I look inside > mywebapp-server\target\mywebapp-server-HEAD-SNAPSHOT.war I see the mywebapp > folder with all the compiled javascript, but no symbolMaps. > > I also tried with: > > value="true" /> > value="true"/> > > Still no symbol maps. > > Any ideas on what I'm missing would be great. Thanks. > > On Sunday 25 February 2024 at 12:45:57 am UTC+11 George Paret wrote: > >> I see the symbolmaps generated in ` >> target/gwt/deploy//symbolMaps ` >> >> I believe it is generated by default. >> >> On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote: >> >>> The symbol maps worked great with the Eclipse GWT plugin compiler. >>> >>> Now switched to use the Maven compiler (with the >>> https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't >>> see the symbol maps anywhere when doing a mvn clean package. >>> >>> Do I need to do something extra to get them? >>> >>> Thanks. >>> >>> On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote: >>> Thank you Alexander! That's what I was missing. Called: exception = SerializableThrowable.fromThrowable(exception); before sending to the server, and now the stack traces show perfectly. :-) >>> -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/ae4ca692-8890-406a-8b6b-44eaa5412e3cn%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Hi George, What I did was: 1. Run https://github.com/tbroyer/gwt-maven-archetypes to generate the sample app. 2. Modify module.gwt.xml to have: 3. Run mvn clean package. Then when I look inside mywebapp-server\target\mywebapp-server-HEAD-SNAPSHOT.war I see the mywebapp folder with all the compiled javascript, but no symbolMaps. I also tried with: Still no symbol maps. Any ideas on what I'm missing would be great. Thanks. On Sunday 25 February 2024 at 12:45:57 am UTC+11 George Paret wrote: > I see the symbolmaps generated in ` > target/gwt/deploy//symbolMaps ` > > I believe it is generated by default. > > On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote: > >> The symbol maps worked great with the Eclipse GWT plugin compiler. >> >> Now switched to use the Maven compiler (with the >> https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't >> see the symbol maps anywhere when doing a mvn clean package. >> >> Do I need to do something extra to get them? >> >> Thanks. >> >> On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote: >> >>> Thank you Alexander! That's what I was missing. >>> >>> Called: >>> exception = SerializableThrowable.fromThrowable(exception); >>> >>> before sending to the server, and now the stack traces show perfectly. >>> :-) >>> >> -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/693aea27-01f7-4bde-92df-2a8faa8fbbc2n%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
I see the symbolmaps generated in ` target/gwt/deploy//symbolMaps ` I believe it is generated by default. On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote: > The symbol maps worked great with the Eclipse GWT plugin compiler. > > Now switched to use the Maven compiler (with the > https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't > see the symbol maps anywhere when doing a mvn clean package. > > Do I need to do something extra to get them? > > Thanks. > > On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote: > >> Thank you Alexander! That's what I was missing. >> >> Called: >> exception = SerializableThrowable.fromThrowable(exception); >> >> before sending to the server, and now the stack traces show perfectly. >> :-) >> > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c99026dd-36b6-4780-9e8e-055d9839789an%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
The symbol maps worked great with the Eclipse GWT plugin compiler. Now switched to use the Maven compiler (with the https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't see the symbol maps anywhere when doing a mvn clean package. Do I need to do something extra to get them? Thanks. On Saturday 18 May 2019 at 8:48:47 am UTC+10 Craig Mitchell wrote: > Thank you Alexander! That's what I was missing. > > Called: > exception = SerializableThrowable.fromThrowable(exception); > > before sending to the server, and now the stack traces show perfectly. :-) > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/27634127-7067-4bc7-b958-2043b61f3f46n%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Thank you Alexander! That's what I was missing. Called: exception = SerializableThrowable.fromThrowable(exception); before sending to the server, and now the stack traces show perfectly. :-) -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/2282e254-fad7-48f3-9cfa-f5ff79de8d10%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Do you wrapping exception with SerializableThrowable (com.google.gwt.core.shared.SerializableThrowable.fromThrowable(Throwable)) before sending to server? On Friday, May 17, 2019 at 12:56:33 AM UTC+3, Craig Mitchell wrote: > > I also tried compiling with Pretty and Detailed, both with the same result > as Obfuscated. > > When I debug the exception passed back to the server, the exception > doesn't have any detail about the JS line that is occurred. So, I don't > understand how the StackTraceDeobfuscator would ever work? > > [image: Annotation 2019-05-17 075404.png] > > Any help much appreciated. > > Thanks again! :-) > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1fcaed24-3d74-4882-be21-4c645ecc3af7%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
I also tried compiling with Pretty and Detailed, both with the same result as Obfuscated. When I debug the exception passed back to the server, the exception doesn't have any detail about the JS line that is occurred. So, I don't understand how the StackTraceDeobfuscator would ever work? [image: Annotation 2019-05-17 075404.png] Any help much appreciated. Thanks again! :-) -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/32045204-772d-4889-a8aa-b4baa8fb9ea1%40googlegroups.com.
Re: Deobfuscated stack trace message and line-specific stack traces
Using GWT 2.8.2. I started seeing errors being picked up by the GWT.setUncaughtExceptionHandler. So, I implemented the StackTraceDeobfuscator by adding the following to my .gwt.xml: Passing the exception back to the server RemoteServiceServlet, and doing the following: String path = getServletConfig().getServletContext().getRealPath( "/WEB-INF/deploy//symbolMaps/"); StackTraceDeobfuscator deobfuscator = StackTraceDeobfuscator.fromFileSystem( path); String strongName = getThreadLocalRequest().getHeader(RpcRequestBuilder. STRONG_NAME_HEADER); // Deobfuscate the stack trace deobfuscator.deobfuscateStackTrace(exception, strongName); // Convert the stack trace to a string StringWriter sw = new StringWriter(); PrintWriter pw = new PrintWriter(sw); exception.printStackTrace(pw); stackTrace = sw.toString(); Now, when I look at what is saved in stackTrace, it is things like this: java.lang.ClassCastException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance( NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader. instantiate(ServerSerializationStreamReader.java:1110) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader. deserialize(ServerSerializationStreamReader.java:682) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader. readObject(ServerSerializationStreamReader.java:592) at com.google.gwt.user.server.rpc.impl. ServerSerializationStreamReader$ValueReader$8.readValue( ServerSerializationStreamReader.java:149) at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader. deserializeValue(ServerSerializationStreamReader.java:434) at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:312) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall( RemoteServiceServlet.java:296) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost( RemoteServiceServlet.java:373) at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost( AbstractRemoteServiceServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter( ServletHandler.java:1772) at team.drift.server.ServletFilter.doFilter(ServletFilter.java:37) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter( ServletHandler.java:1759) at com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter. doFilter(JdbcMySqlConnectionCleanupFilter.java:60) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter( ServletHandler.java:1759) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java: 582) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java :143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java: 524) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler. java:226) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java :143) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper. java:134) at com.google.apphosting.runtime.jetty9.ParseBlobUploadHandler.handle( ParseBlobUploadHandler.java:119) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler. java:1182) at com.google.apphosting.runtime.jetty9.AppEngineWebAppContext.doHandle( AppEngineWebAppContext.java:183) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512 ) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler. java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler. java:1112) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java :141) at com.google.apphosting.runtime.jetty9.AppVersionHandlerMap.handle( AppVersionHandlerMap.java:293) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper. java:134) at org.eclipse.jetty.server.Server.handle(Server.java:539) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) at com.google.apphosting.runtime.jetty9.RpcConnection.handle(RpcConnection. java:213) at com.google.apphosting.runtime.jetty9.RpcConnector.serviceRequest( RpcConnector.java:81) at com.google.apphosting.runtime.jetty9.JettyServletEngineAdapter. serviceRequest(JettyServletEngineAdapter.java:123) at com.google.apphosting.runtime.JavaRuntime$RequestRunnable. dispatchServletRequest(JavaRuntime.java:692) at com.google.apphosting.runtime.JavaRuntime$RequestRunnable. dispatchRequest(JavaRuntime.java:655) at
Re: Deobfuscated stack trace message and line-specific stack traces
Hi, I do not know about version 2.8, but for 2.6 we did next: - put value "PRETTY" in the pom.xml for gwt plugin - put next loggin settings in the application gwt config file as result we had a proper class names and line numbers in the stack-trace massages понеділок, 5 листопада 2018 р. 19:59:15 UTC+1 користувач brad написав: > > 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Deobfuscated stack trace message and line-specific stack traces
Depending on your browser versions you support, you could try enabling source maps for other user agents as well. Currently it is only active for safari permutation. If you deploy the generated source maps, the StackTraceDeobfuscator could use them on the server to make better stack traces. You would need to add some additional rebind rules to your project in the same manner as in https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/core/CoreWithUserAgent.gwt.xml At the end it all depends on wether or not the browser reports column numbers in addition to line numbers then throwing an error. Because in GWT generated JS every method has its own line and is a one-liner (white spaces, new lines within method removed) itself, browsers which only report line numbers basically only report the JS method that caused the error. Only with a column number it is possible to also figure out the expression within the method. Of course GWT could technically produce a JS file which has every single statement/expression on its own line, but that would add a significant amount of new line characters and thus would make your app larger (even though gzip compression might mitigate that issue). If GWT would do that, then column numbers wouldn't be required. Using the above source maps based solution only works in browsers which support column numbers because source maps encoding is based on column numbers. See http://www.mattzeunert.com/2016/02/14/how-do-source-maps-work.html if interested. -- J. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Deobfuscated stack trace message and line-specific stack traces
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 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 google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
