Support source mapping of stack traces in the Debug Console

[roblourens]

From @auchenberg on March 22, 2016 22:11

When an error is thrown with a stack trace, we should support source mapping of the source:

Actual:

Click on Scope.$scope.onAddNewClick (http://localhost:8080/app_bundled.js:234:5) triggers:

Expected:
Path to files within stack traces are source mapped to the original source.

Copied from original issue: Microsoft/vscode-chrome-debug#132

[nojvek]

@roblourens Seems like this issue has been open for a while. I can take a stab at it if you're busy with other tasks. Let me know.

[auchenberg]

@nojvek Please hack away, if time allows it :)

[roblourens]

That would be cool. I don't have any immediate plan to work on this.

[auchenberg]

Landed in #190

[nojvek]

Just curious, how often do you release updates to the chrome debug plugin? Also do you envision the plugin to be part of vscode install by default?

…

On Thu, Mar 23, 2017 at 10:55 AM, Kenneth Auchenberg < ***@***.***> wrote: Landed in #190 <#190> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVCV9xuq-W7euYEH3zGAMHsvRuigoks5rorIigaJpZM4IXs92> .

[auchenberg]

We release as needed, and for know we don't ship out of the box until we have a better way to enable remote debugging in Chrome (and other browsers). On Fri, Mar 24, 2017 at 5:24 PM Manoj Patel <[email protected]> wrote:

…

Just curious, how often do you release updates to the chrome debug plugin? Also do you envision the plugin to be part of vscode install by default? On Thu, Mar 23, 2017 at 10:55 AM, Kenneth Auchenberg < ***@***.***> wrote: > Landed in #190 > <#190> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #6 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AA-JVCV9xuq-W7euYEH3zGAMHsvRuigoks5rorIigaJpZM4IXs92 > > . > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKl9_qdN0VFGvTJyrvDuiUzuB2Tyx5Lks5rpF7BgaJpZM4IXs92> .

[roblourens]

I update it whenever I have time to test, and write a changelog and stuff. Planning on doing it by today or tomorrow.

Probably will stay a separate extension for the time being.

[nojvek]

Makes sense. node2 inspect debugger ends up using the same core as chrome debugger though right?

…

On Fri, Mar 24, 2017 at 5:40 PM Rob Lourens ***@***.***> wrote: I update it whenever I have time to test, and write a changelog and stuff. Planning on doing it by today or tomorrow. Probably will stay a separate extension for the time being. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVFSo2ULHnRrvTouLxWq8JWHELhD0ks5rpGJvgaJpZM4IXs92> .

[roblourens]

Yep, also I just updated the chrome extension :)

[nojvek]

⛄️🎉🎊💫✨🎈💥🔥

…

On Fri, Mar 24, 2017 at 7:14 PM Rob Lourens ***@***.***> wrote: Yep, also I just updated the chrome extension :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA-JVD9Op0EjbxCSg7cPEIiBBxQf9U85ks5rpHiXgaJpZM4IXs92> .

[aramando]

Any ideas why this still isn't working for me? I am running the latest versions of Code and the Chrome Debug extension, and my webRoot launch config property is set right. Do you have to have sourcemap files for the JS files in question, even if they wouldn't ordinarily need one?

[roblourens]

I just (like an hour ago) updated it to map from URL to local file, if you aren't using sourcemaps. If you are using sourcemaps, then it should work if setting BPs and debugging with sourcemaps works.

[aramando]

Oh, fantastic! So I just need to wait for that to make it into the next release of the extension? Any idea roughly what kind of timeframe that might occur in?

[roblourens]

The release went out today, it's in 2.7.3 if you don't already have that

[aramando]

Oh, I am already running that, but it's still not working :-/

[roblourens]

Can you open another issue with details?

[AskYous]

Hey @roblourens, I am also receiving an error saying it cannot find the file. I am running Debugger for Chrome version 3.1.2. I posted a screenshot below. Notice a couple of things:

1. My website is running on localhost:1337. For some reason, VSCode is trying to open the file in /1337/js/components.js. (How did the port get into the source path???)
2. I have source mapping on for my typescript files.
3. The file open is the launch.json file shown in the screenshot. I pointed the webRoot folder to my assets folder, yet it seems to completely ignore it.

[roblourens]

That's strange, but a different problem, can you open a new issue?

Can you also set "trace": true in your launch config, repro this again, and include the log?

[AskYous]

@roblourens Sure, I'm on it. I got here through a google search. Question: where does the debug info log into when I turn trace on in Windows 10? I don't know where it is.

[roblourens]

Thanks - it writes a log file and prints the path at the top of the console.

[AskYous]

Ok. I opened #212.