Also telling your JS debugger to pause on uncaught exceptions will help - it will stop when that null.toString() takes place, letting you examine which method you are in when it happens, and which local variable or field is null.
On Wednesday, March 13, 2019 at 3:33:48 PM UTC-5, Jens wrote: > > Why don't you just look at the JavaScript in Chrome to see if GWT compiler > did some easy optimizations which cause your stepping though source maps > look strange. > > Especially if you start SDM using -style PRETTY and > -XmethodNameDisplayMode you can understand the JS relatively well, even > without deep JS knowledge. > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
