break point not working

[1057437122]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version:
• OS Version:

Steps to Reproduce:

1.upgrade to latest vscode => 1.59.1
2.start an expressjs + typescript project
3.create a launch.json file:

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "trace": true,
      "request": "launch",
      "name": "Launch Program",
      "skipFiles": [
        "<node_internals>/**"
      ],
      "program": "${workspaceFolder}/index.js",
      "preLaunchTask": "tsc: build - tsconfig.json",
      "outFiles": [
        "${workspaceFolder}/dist/**/*.js"
      ],
    }
  ]
}

4. start debugger:

the debugger started in a second, even it's still building the project, and after a while the debug console panel doesn't have any logs. I tested the project with curl or chrome, the project is running, cuz I got the expected results. I created a break point , but it didn't stop there.
When I stop the debugger, the debug console panel start to show all the logs: request log, debug log and so on...

[connor4312]

/jsDebugLogs

[1057437122]

connor@xbox.com

Thanks, I've sent the full log to that email, and I think the useful information I found is on this picture, but I don't know how to solve the problem.

I have also tried this:

$:sudo rm -rf $HOME/Library/Application\ Support/Code
$:sudo rm -rf $HOME/.vscode-react-native
$:sudo rm -rf $HOME/.vscode

and uninstall vscode application.

After a restarting of my computer, I reinstalled from brew.
After the new clean installation, the breakpoint worked! But only once, after I changed some of my code in my project and restarted the debugger(my expressjs + typescript project), the breakpoint stoped working again! But this time is a little different, before this, the breakpoint said is unbound, but this time the breakpoint status seemed correct, which means its color is red , but it never stop at the breakpoint.

I also tried another Python project, same error, breakpoint added successfully and its color is red, but it never stop at these points.

[connor4312]

It looks like you're starting your program with "Run Without Debugging" (i.e. not in debug mode). This prevents breakpoints from being bound -- in any runtime.

You can use F5 or the green arrow in the Debug view to start your program in debug mode.

[1057437122]

How to "Run Withou Debugging" ?

There're three ways here in my computer:

1. press F5 => debugger started and breakpoint said: unbound breakpoint( color grey)
2. press green arrow in the Debug view => same as using F5
3. press green arrow in touch bar(mac book pro) => breakpoint status seem correct(red), but it never stop at these points.

I think none of the three works as-designed

[connor4312]

If it's grey that means you are debugging but the breakpoint didn't bind. If you get a trace log in that state, I can take a look at it.

[1057437122]

Hello bro, the trace log(-4c9dacf8) was created by pressing the green button in debug view. => break point is grey and said unbound [image: Captura de pantalla 2021-09-03 a las 19.41.26.png]

…

On Fri, Sep 3, 2021 at 7:34 PM Connor Peet ***@***.***> wrote: If it's grey that means you are debugging but the breakpoint didn't bind. If you get a trace log in that state, I can take a look at it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#132119 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSS6AFH4BX7YNND74QBBVDUAEBJ7ANCNFSM5DI5U72A> .

[1057437122]

sorry I just found I didn't put the log here, now I did:
vscode-debugadapter-a262c5b2.json.gz
thanks for your help

[jakawell]

We are experiencing a similar issues. We're running Mocha tests in Node with TypeScript. Breakpoints worked fine in 1.59, but once we upgraded to 1.60, the debugger does not stop at breakpoints.

If we set a breakpoint using the JS keyword debugger, it will stop at that line, but it does so in a separate read-only instance of the file.

[connor4312]

@jakawell there's a good chance this will fix it for you: microsoft/vscode-js-debug#1100 (comment)

[jakawell]

@connor4312 Aha, perfect. That solved our issue. Thanks!