> > Well this still does not solve the problem! > Yeah thats true and thats why I said that it currently kind of sucks.
If 1a) would also show the java cause chain then there would be at least one way to get some useable information reliably. Currently the best thing is to stop in the debugger. The debugger (at least Chrome and possibly FireFox) evaluates the display name calculated when using -methodNameDisplayMode and usually uses source maps. IMHO printing/logging stack traces is in most cases useless for now. -- J. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/6e3684de-315f-4912-8788-ca902ff53780%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
