Indeed,
Out of the box (-style OBF) you get:
at Unknown.lG(Unknown Source:0)
at Unknown.Ccb(Unknown Source:0)
at Unknown.kD(Unknown Source:0)
at Unknown.nK(Unknown Source:0)
at Unknown.vO(Unknown Source:0)
at Unknown.cP(Unknown Source:0)
at Unknown.f_(Unknown Source:0)
at Unknown.zK(Unknown Source:0)
at Unknown.p_(Unknown Source:0)
at Unknown.a1(Unknown Source:0)
at Unknown.c1(Unknown Source:0)
at Unknown.anonymous(Unknown Source:0)
If you add in the enhanced web more stack traces (and pay the
JavaScript/runtime overhead):
<inherits name="com.google.gwt.core.EmulateJsStack"/>
<set-configuration-property
name="compiler.emulatedStack.recordLineNumbers" value="true"/>
<set-configuration-property name="compiler.emulatedStack.recordFileNames"
value="true"/>
You get the following, which notably can be pasted into Eclipse's "Stack
Trace Console" view so that the filename:lineNumber pairs become clickable
hyperlinks:
at Unknown.E4(JsArrayString.java:42)
at Unknown.pBb(StackTraceCreator.java:280)
at Unknown.D1(InteractiveDemoPanel.java:135)
at Unknown.a9(com.google.gwt.dev.jjs.impl.GenerateJavaAST:0)
at Unknown.ibb(HandlerManager.java:65)
at Unknown.vbb(HandlerManager.java:178)
at Unknown.yxb(Widget.java:52)
at Unknown.m9(DomEvent.java:116)
at Unknown.cyb(Widget.java:90)
at Unknown.tnb(DOM.java:1322)
at Unknown.vnb(DOM.java:1266)
at Unknown.anonymous(DOMImplStandard.java:180)
On Fri, Jul 31, 2009 at 4:16 PM, Ray Cromwell <[email protected]> wrote:
>
> The way you see this in Java bytecode that has been obfuscated and stripped
> of line number information is, IIRC
> at z.onClick_6(Unknown)
>
> typically you see these on commercial Java software that has thrown an
> exception.
>
> -Ray
>
>
> On Fri, Jul 31, 2009 at 3:48 PM, Bruce Johnson <[email protected]> wrote:
>
>> I prefer "Unknown" because it's an indication you are looking at
>> suboptimal stack trace output. "JavaScript" makes it sound like we actually
>> intend for you to be looking at that output, when in fact, you really want
>> to use symbol maps to reverse lookup the Java idents.
>>
>> On Fri, Jul 31, 2009 at 2:42 PM, Fred Sauer <[email protected]> wrote:
>>
>>> Web mode stack traces are steadily improving. You can even get line
>>> numbers (by inheriting com.google.gwt.core.EmulateJsStack).
>>>
>>> Without the extra instrumentation you web mode stack traces might look
>>> something like this:
>>> at Unknown.$NullPointerException()
>>> at Unknown.onClick_6()
>>> at Unknown.dispatch()
>>> at Unknown.$fireEvent()
>>> at Unknown.$fireEvent_0()
>>> at Unknown.$fireEvent_1()
>>> at Unknown.fireNativeEvent()
>>> at Unknown.onBrowserEvent()
>>> at Unknown.dispatchEventImpl()
>>> at Unknown.dispatchEventAndCatch()
>>> at Unknown.anonymous()
>>>
>>> I was thinking it might make slightly more sense if we replaced 'Unknown'
>>> with 'JavaScript', e.g.
>>>
>>> at JavaScript.$NullPointerException()
>>> at JavaScript.onClick_6()
>>> at JavaScript.dispatch()
>>> at JavaScript.$fireEvent()
>>> at JavaScript.$fireEvent_0()
>>> at JavaScript.$fireEvent_1()
>>> at JavaScript.fireNativeEvent()
>>> at JavaScript.onBrowserEvent()
>>> at JavaScript.dispatchEventImpl()
>>> at JavaScript.dispatchEventAndCatch()
>>> at JavaScript.anonymous()
>>>
>>>
>>> Anyone have strong opinions wither way?
>>>
>>> --
>>> Fred Sauer
>>> Developer Advocate
>>> Google Inc. 1600 Amphitheatre Parkway
>>> Mountain View, CA 94043
>>> [email protected]
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>
--
Fred Sauer
Developer Advocate
Google Inc. 1600 Amphitheatre Parkway
Mountain View, CA 94043
[email protected]
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
