On Thursday, July 18, 2013 3:21:59 PM UTC+2, RyanZA wrote: > > Jens, even with source maps in Chrome, I've been unable to get stack > traces to work. They still print out poorly in production when an exception > is hit - the exceptions ignore the source maps entirely. I asked previously > if there is a way around it, but apparently it's a known issue - so I don't > think SourceMaps solve this problem yet. > > That said, the size and speed overhead here is terrible and most people > would avoid something that adds that much overhead in production (although > it would be great in development). > > What GWT needs here is something closer to what you get with proguard - a > mapping file created during compilation that could be used to run the > obfuscated/javascript exception through a utility to give the correct stack > trace with zero overheads. > I'm not entirely sure on how proguard accomplishes it, but I'd say it > would be the perfect solution. >
This is what the StackTraceDeobfuscator does already. It's currently based on symbolMaps (GWT-specific) rather than source maps though. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
