Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

stopOnEntry doesn't work

See original GitHub issue

Issue Type: Bug

vs code didnt start debug after the node program on remote server is executed. port 9229 is forwarded from remote to local if i close vs code and try it with chrome://inspect in the crhome browser. the debug session is shown and i can start it

Extension version: 0.84.0 VS Code version: Code 1.69.1 (b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a, 2022-07-12T08:21:24.514Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No Remote OS version: Linux x64 4.19.0-18-amd64

System Info

Item	Value
CPUs	Intel® Core™ i7-6700K CPU @ 4.00GHz (8 x 4008)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.93GB (9.41GB free)
Process Argv	–crash-reporter-id bbd4b258-0071-4bdb-a494-98887c18d752
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: 192.168.1.61
OS	Linux x64 4.19.0-18-amd64
CPUs	Intel® Celeron® CPU J3455 @ 1.50GHz (4 x 2196)
Memory (System)	15.52GB (0.94GB free)
VM	0%

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30525689
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

Issue Analytics

State:
Created a year ago
Comments:16 (6 by maintainers)

Top GitHub Comments

1reaction

oweitmancommented, Oct 5, 2022

thank you. that was the solution

0reactions

connor4312commented, Oct 5, 2022

You can run sudo setcap -r $(which node) to unset any capabilities that were previously set

Top Results From Across the Web

Visual Studio Code - stopOnEntry does not work with python

i've try to use VSCode for my python development. Everything works fine, but i have one problem. The stopOnEntry debug settings seems not ......

Debugging in Visual Studio Code

One of the great things in Visual Studio Code is debugging support. Set breakpoints, step-in, inspect variables and more.

Debugging in VS Code suddenly stopped working

Hi everyone, I'm having some trouble debugging my julia code in VS Code and it's getting me out of my mind. It possibly...

Configuration | Vimspector Documentation

The launch configuration requires stopOnEntry to be a bool. This doesn't work: "stopOnEntry": "${StopOnEntry}". The reason is that if the user types true ......

launch.vs.json schema reference (C++) - Microsoft Learn

In Visual Studio 2017 and later versions, you can open and build code ... Normally, you don't need to change this value when...