I haven't had a look at GWT 2.5 yet in any detail, but I'd suggest starting by using the debugger to step through the the code that tries to get the symbolMap and make sure it's able to see and open the file.
On Fri, Nov 9, 2012 at 3:54 AM, Ken Kahn <[email protected]> wrote: > I have been successfully using gwt-log and stack deobfuscation for a long > time but it recently stopped working and I get > > com.allen_sauer.gwt.log.server.ServerLogImplJDK14 log: Failed to > deobfuscate stack trace for permutation 65EA13183F23F5F8EC3B08A6B2F2F6CC. > Verify that the corresponding symbolMap is available. > > I don't know if upgrading to 2.5, experimenting with Super Dev Mode (I may > have followed some instructions for generating Symbol maps for debugging in > Chrome), or something else is causing the problem. But I can see the files > in WEB-INF/deploy/Model/symbolMaps/ > > I use the Eclipse plugin to deploy. And I use the Google App Engine. > > Any suggestions? > > -- > You received this message because you are subscribed to the Google Groups > "gwt-log" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/gwt-log/-/Uvwds0RnivYJ. > 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/gwt-log?hl=en. > -- Fred Sauer [email protected] -- You received this message because you are subscribed to the Google Groups "gwt-log" group. 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/gwt-log?hl=en.
