New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 619624 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 581017
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Use source maps to normalize stack traces

Reported by oliverj...@gmail.com, Jun 13 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2763.0 Safari/537.36

Steps to reproduce the problem:
1. Console log new Error().stack from within a file with a source map

What is the expected behavior?
The printed stack trace should be resolved against the source map.

What went wrong?
It is not resolved against the source map.

Did this work before? N/A 

Chrome version: 53.0.2763.0  Channel: dev
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 22.0 r0

This only happens when logging stack traces manually. This is quite common practice, e.g. console.error(error.stack);
 
Cc: yangguo@chromium.org
Components: Platform>DevTools>JavaScript
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Mergedinto: 581017
Status: Duplicate (was: Assigned)

Sign in to add a comment