Re: Any issues running in detailed (or pretty) style in production?

[Paul Robinson]

We've done this for a long time now, and it does indeed work well. You
don't get the exact line numbers, but rather the first line number of the
method it's in, but that's usually enough. We also have an extra
permutation for a "debug" build that sets compiler.stackMode to emulated. I
set it up so you have to point your web browser at a different landing page
to get this permutation, so customers don't normally see it. However, it's
easy to use it ourselves (in testing or production) or to point somebody at
it if we need more accurate stack traces.

We always ship the standard and debug versions with every release, so we
can always use the debug version that's the equivalent of what's in
production.

Paul

On Fri, Jun 9, 2017 at 8:38 AM, Jens  wrote:

>
> No, because I just figured the obfuscated code wasn't worth trying to
>> deobfuscate, but apparently symbolMaps is the key.  Kirill provded the
>> details so I plan to refer to that.  Thanks for the time!
>>
>
> As a future improvement: You could send any client side exception to the
> server using the GWT UncaughtExceptionHandler and then let the server
> deobfuscate the exception (SymbolMaps/SourceMaps + StackTraceDeobfuscator)
> and log it. Alternatively the deobfuscated exception could also be send via
> mail (possibly encrypted) to a bug tracker or similar. Works pretty well.
>
> -- 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.
>

-- 
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: Any issues running in detailed (or pretty) style in production?

[Jens]

> No, because I just figured the obfuscated code wasn't worth trying to 
> deobfuscate, but apparently symbolMaps is the key.  Kirill provded the 
> details so I plan to refer to that.  Thanks for the time!
>

As a future improvement: You could send any client side exception to the 
server using the GWT UncaughtExceptionHandler and then let the server 
deobfuscate the exception (SymbolMaps/SourceMaps + StackTraceDeobfuscator) 
and log it. Alternatively the deobfuscated exception could also be send via 
mail (possibly encrypted) to a bug tracker or similar. Works pretty well.

-- 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: Any issues running in detailed (or pretty) style in production?

[Robert J. Carr]

> Have you tried working your way into the symbolMaps?​

No, because I just figured the obfuscated code wasn't worth trying to
deobfuscate, but apparently symbolMaps is the key.  Kirill provded the
details so I plan to refer to that.  Thanks for the time!

-- 
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: Any issues running in detailed (or pretty) style in production?

[Robert J. Carr]

Great, thanks so much for this information, I'll study it and run some
tests, but I'm sure it will create some great leads.  Cheers!

-- 
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: Any issues running in detailed (or pretty) style in production?

[Thomas Broyer]

On Wednesday, June 7, 2017 at 9:39:55 PM UTC+2, rjcarr wrote:
>
> I've been using GWT for years and years but recently my customers have a 
> problem that I can't reproduce, and they're remote so I can't just go check 
> it out in person.
>
> They're getting an unresponsive script error, and the browser will tell 
> them where it is, but the code is obfuscated.  
>

Have you tried working your way into the symbolMaps? (that's how the 
StacktraceDeobfuscator works fwiw)

-- 
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: Any issues running in detailed (or pretty) style in production?

[Kirill Prazdnikov]

We use single permutation (safari) for all browsers, if you do not, you 
have to look at
 
  target\projectName-1.0-SNAPSHOT\projectName\compilation-mappings.txt

in order to understand which script is current.

Then go to 

target\projectName-1.0-SNAPSHOT\WEB-INF\deploy\projectName\symbolMaps

Here you will find a map file for each permutation with something like 

Yr,com.google.gwt.user.client.Timer::clearTimeout(I)V,com.google.gwt.user.client.Timer,clearTimeout,com/google/gwt/user/client/Timer.java,154,0

this means that function Yr(...){...} is Timer::clearTimeout


-- 
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: Any issues running in detailed (or pretty) style in production?

[Kirill Prazdnikov]

just look in to the directory and look into the files. damn easy
i don't remember exactly (can build my project and write later)

среда, 7 июня 2017 г., 23:54:42 UTC+3 пользователь rjcarr написал:
>
> > There is a file (produces during build) with all names mapping to java 
> methods. You can de-obfuscate it manually.
>
> This sounds like exactly what I need.  Not to take more of your time, but 
> do you have any references where I can get more information about this?
>
> Thanks!
>

-- 
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: Any issues running in detailed (or pretty) style in production?

[Robert J. Carr]

> There is a file (produces during build) with all names mapping to java
methods. You can de-obfuscate it manually.

This sounds like exactly what I need.  Not to take more of your time, but
do you have any references where I can get more information about this?

Thanks!

-- 
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: Any issues running in detailed (or pretty) style in production?

[Kirill Prazdnikov]

Hi

They're getting an unresponsive script error, and the browser will tell 
> them where it is, but the code is obfuscated.
>

It is not an issue if you have obfuscated stack trace. There is a file 
(produces during build) with all names mapping to java methods. You can 
de-obfuscate it manually. Just get crash (or exception) stack screenshot 
from them.

 

>  I'm out of ideas for trying to reproduce, but I was thinking if I 
> compiled the code as detailed (or pretty, what's the difference?), 
>

I recommend you pretty if you go this ways. It is easy readable and not so 
huge (as detailed).

Another recommendation - ask them to run TeamViewerQuickSupport and ask 
them to call you when the problem happens so that you can examine the stack 
trace (or even debug, the classes still have correct class type information 
with names). (in this.proto._class_)

-- 
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: Any issues running in detailed (or pretty) style in production?

[Robert J. Carr]

Thanks for the response, and yes, totally inaccessible by any means.

So back to my main question: are there any serious ramifications, mostly
related to runtime (as I understand the issues with loading), with running
a non-obfuscated application?
​
Thanks!

-- 
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: Any issues running in detailed (or pretty) style in production?

[Vassilis Virvilis]

If your production site is not remotely accessible then there is nothing
you can do. You have to go there.

If the site is accessible from your browser (even with ssh tunnels) the
technique I suggested is employable.

   Vassilis

On Wed, Jun 7, 2017 at 11:13 PM, Robert J. Carr  wrote:

> Hi Vassillis-
>
> Thanks for the response.  A few comments:
>
> > the problem is reproducible in the remote system and not just happens
> after several hours of usage
>
> It's not entirely reproducible, but does seem to happen with some
> regularity.  And yes, it has hours of usage, which could be the problem.
>
> > it is a client side error and not a server side error
>
> Definitely client side.
>
> But the rest of what you say I don't completely understand.  Yes, it is
> running https, but I should have been clear, I also don't have access to
> the server.  I don't have access to anything as it is all on a remote
> private network.
>
> Sorry for the confusion.
>
>
> --
> 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.
>



-- 
Vassilis Virvilis

-- 
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: Any issues running in detailed (or pretty) style in production?

[Robert J. Carr]

Hi Vassillis-

Thanks for the response.  A few comments:

> the problem is reproducible in the remote system and not just happens
after several hours of usage

It's not entirely reproducible, but does seem to happen with some
regularity.  And yes, it has hours of usage, which could be the problem.

> it is a client side error and not a server side error

Definitely client side.

But the rest of what you say I don't completely understand.  Yes, it is
running https, but I should have been clear, I also don't have access to
the server.  I don't have access to anything as it is all on a remote
private network.

Sorry for the confusion.

-- 
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: Any issues running in detailed (or pretty) style in production?

[Vassilis Virvilis]

Here is an idea assuming
 a) the problem is reproducible in the remote system and not just happens
after several hours of usage
 b) it is a client side error and not a server side error

You can try to use bookmarklets for compilation in super dev mode. There
are some hurdles to overcome, especially in a https site. I have documented
all as best as I could in
https://vasvir.wordpress.com/2017/02/07/gwt-super-dev-mode-https-setup-in-7-steps/

This way you will be able to debug with --preety from your development
machine without interfering with normal visitor - you will be the only one
seeing the --preety code.

Hope that helps.

 Vassilis

On Wed, Jun 7, 2017 at 10:39 PM, rjcarr  wrote:

> I've been using GWT for years and years but recently my customers have a
> problem that I can't reproduce, and they're remote so I can't just go check
> it out in person.
>
> They're getting an unresponsive script error, and the browser will tell
> them where it is, but the code is obfuscated.
>
> I'm out of ideas for trying to reproduce, but I was thinking if I compiled
> the code as detailed (or pretty, what's the difference?), then they'd have
> a better chance at reporting back the problem.
>
> So my question is, what are the ramifications of a non-obfuscated
> compile?  Obviously the javascript files will be (much) bigger, and besides
> an obviously longer download it will likely take the browser a bit longer
> to parse and load, but I assume there shouldn't be any issues beyond that?
>
> Thanks!
>
> --
> 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.
>



-- 
Vassilis Virvilis

-- 
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.