From:  Joey Schorr <jschorr@gmail.com>
Date:  18 Mar 2014 07:50:26 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.js-sourcemap
Subject:  

Re: better document the "names" field in Source Maps

NNTP-Posting-Host:  63.245.216.66

The intention was to both deobfuscate stack traces and provide a way for
de-minimization of source code if the mapping was semi-direct. The old
Closure Inspector (https://code.google.com/p/closure-inspector/) would
actually use the names to remap the source code view inline, but this
obviously only applied to the Closure case where the input language was
also (basically) JavaScript.


On Mon, Mar 17, 2014 at 7:41 PM, Brian Slesinsky wrote:

> (Sending this to the list since I can't comment directly on the document.)
>
> Re:
>
> https://docs.google.com/a/google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit#
>
> A comment on this line:
>   Line 7: A list of symbol names used by the "mappings" entry.
>
> I think the spec should explain a bit more about how this is typically
> used. Despite doing a fair amount of work with sourcemaps, I was unclear on
> this until recently.
>
> As far as I know no debugger uses the "names" field, but the intention is
> to deobfuscate stack traces. That is, when a JavaScript exception occurs or
> a debugger stops at a breakpoint, we can treat the stack trace as a list of
> positions in JavaScript files. For each position, the "name" is the
> deobfuscated function name that should appear in the stack trace. (Or more
> generally, it is whatever string would most usefully appear in the function
> name position when displaying a stack frame in the debugger.)
>
> - Brian
> _______________________________________________
> dev-js-sourcemap mailing list
> dev-js-sourcemap@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-js-sourcemap
>