Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Breakpoint set but not yet bound

I wanted to use vscode extension ( Debugger for Chrome ), but whatever I try I can't get rid of the 'breakpoint set but not yet bound'.

Everything is running, the debugger console is showing all the console log messages but I can hit the debug point.

Here is my launch.json

{
      "type": "chrome",
      "request": "launch",
      "name": "Launch Chrome against localhost",
      "url": "http://localhost",
      "webRoot": "${workspaceFolder}/client/",
      "sourceMaps": true,
      "sourceMapPathOverrides": {
        "webpack:/*": "${webRoot}/*"
      }
    }

I am using Angular and its running inside Docker. Any help will be appreciated.

like image 208
Aslam Avatar asked Oct 10 '19 11:10

Aslam


People also ask

What does'breakpoint set but not yet bound'mean?

"Breakpoint set but not yet bound" is displayed when hovering over the breakpoint. Debugger is working just fine, when pressing the pause button the execution stops. Console log shows that the code is running in the file where the breakpoint is set.

How to set breakpoint in Visual Studio 2019?

Breakpoint set but not yet bound in Visual Studio 2019 1 clean and rebuild 2 Set the startup project 3 Deleted temp files and rebuild 4 update and restart system etc.. More ...

How are breakpoints bound to the code or data?

First, the breakpoint must be described, and then, as code or data becomes available, it must be bound to that code or data, as follows: The breakpoint is requested from the relevant debug engines (DEs), and then the breakpoint is bound to the code or data as it becomes available.

How to fix resolving breakpoint is not working?

Resolving breakpoint will not be hit error ways. We will start with simple solution, try to clean your solution and then re-build. For this, simply open your "Solution Explorer", select your "Solution" and right click on it, Select "Clean Solution", once solution is cleaned, which will delete all the compiled and temporary files associated ...


2 Answers

Your launch.json should be as follows

{
   "type": "chrome",
   "request": "launch",
   "name": "Launch Chrome",
   "url": "http://localhost:4200",
   "webRoot": "${workspaceFolder}",
   "sourceMaps": true,
   "sourceMapPathOverrides": {
       "/./*": "${webRoot}/*",
       "/src/*": "${webRoot}/*",
       "/*": "*",
       "/./~/*": "${webRoot}/node_modules/*"
    }
}
like image 192
Pac-Man Avatar answered Oct 27 '22 00:10

Pac-Man


Make sure your webRoot setting is pointing to the right directory of your angular project. It's likely that your ${workspaceFolder} is referring to the top-level directory.

for example: Your source code is in C:\projects\awesome_tool\client but, your ${workspaceFolder} is pointing to C:\projects. To fix this, you need to modify webRoot's value in launch.json file as webRoot": "${workspaceFolder}/awesome_tool/client

like image 31
Nagesh Andani Avatar answered Oct 27 '22 01:10

Nagesh Andani