Thanks for that, I am now generating multiple permutations, and have updated the stackoverflow question with this information.
On Thursday, May 31, 2012 10:27:57 AM UTC-5, cueman wrote: > > You can deobfuscate non-emulated stack traces. Check out > com.google.gwt.logging.server.StackTraceDeobfuscator > > You need to arrange for the symbol maps created at compile time to be > available. > > Note that you can also set up another permutation so that you have > emulated stack traces or not, and set up two host html files to choose > whether emulated stack traces are on. That way, you can have a production > compile that most people use, but then occasionally you can switch to see > the same thing with emulated stacks turned on. > > Emulated stacks tend to show slightly different information from > deobfuscated stack traces. > > HTH > Paul > > On 31/05/12 15:58, wytten wrote: > > I'm looking for practical advice here; we have a GWT application in > pre-production pilot. > > It is working rather well, but occasionally transient client errors > occur. > > We are using an uncaught exception handler, but the information that it > reports is > > very sparse (For example in IE6, "Object doesn't support this property > or method") > > > > I've tried turning on emulated stack traces in development, but due to > performance > > problems (See http://stackoverflow.com/questions/10740608) > > I haven't been able to leave it turned on, and therefore it is not > active in the pilot environment. > > > > What else I can do to track down these issues? In one case the problem > consistently happens > > on 2 or 3 client machines, but not on any of the others. > > > > Regarding the practical usability of emulated stack traces, I'm > surprised that no one else seems > > to have reported this problem. Only yesterday I had a similar > experience in development where > > I thought using emulated stack traces would save the day, only to be > disappointed again that > > turning them on made the application unusable. (I believe this is a > client memory issue) > > Should I open a GWT issue? A possible enhancement that comes to mind is > to create emulated > > stack traces only for certain packages, to conserve memory. > > > > Thanks. > > -- > > You received this message because you are subscribed to the Google > Groups "Google Web Toolkit" group. > > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/rdEzO0eYi8MJ. > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > [email protected]. > > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/snPQPsCF7QoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
