Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

debug hover failed when using chrome debugger #18501

Closed
f111fei opened this issue Jan 13, 2017 · 1 comment
Closed

debug hover failed when using chrome debugger #18501

f111fei opened this issue Jan 13, 2017 · 1 comment
Assignees
@isidorn
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone
January 2017

Comments

@f111fei
Copy link
Contributor

f111fei commented Jan 13, 2017

  • VSCode Version: Code - Insiders 1.9.0-insider (2cdc2b3, 2017-01-13T07:09:47.827Z)
  • OS Version: Windows_NT ia32 6.1.7601
  • Extensions:
Extension Author Version
debugger-for-chrome msjsdiag 2.4.2

Steps to Reproduce:

  1. create index.js
function fuck() {
    var error;
    console.log(error.fuck);
}
fuck();
  1. create index.html
<!DOCTYPE HTML>
<html>
<head>
    <meta charset="utf-8">
    <title>Test</title>
	<script src="./index.js"></script>
</head>
</html>
  1. create .vscode/launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Chrome against localhost",
            "type": "chrome",
            "request": "launch",
            "file": "${workspaceRoot}/index.html",
            "webRoot": "${workspaceRoot}"
        }
    ]
}

  1. Launch chrome debugger. the debugger will paused in exception.

  2. Hover the text fuck.

  3. Toggle VSCode DevTools will find the error log.

Cannot read property 'startLineNumber' of null: TypeError: Cannot read property 'startLineNumber' of null
    at Function.e.containsRange (file:///C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/electron-browser/workbench.main.js:40:10005)
    at file:///C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/electron-browser/workbench.main.js:101:6764
    at Array.filter (native)
    at file:///C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/electron-browser/workbench.main.js:101:6730
    at then (file:///C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/electron-browser/workbench.main.js:32:17375)
    at e.findExpressionInStackFrame (file:///C:/Program Files (x86)/Microsoft VS Code Insiders/resources/app/out/vs/workbench/electron-browser/workbench.main.js:101:6658)

The reason for this bug is 524150b to fix #16632

I add a comment for the commit.
f111fei referenced this issue Jan 13, 2017
@isidorn
Find the most specific scope containing the range
524150b 
fixes #16632
@f111fei f111fei closed this as completed Jan 13, 2017
@f111fei
Copy link
Contributor Author

f111fei commented Jan 13, 2017

fixed in 4dcbad3

@isidorn isidorn self-assigned this Jan 13, 2017
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Jan 13, 2017
@isidorn isidorn added this to the January 2017 milestone Jan 13, 2017
@roblourens roblourens added the verified Verification succeeded label Jan 26, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Milestone
January 2017
Development

No branches or pull requests
3 participants
@roblourens @isidorn @f111fei