vscode: Sourcemaps (breakpoints) when attaching to a node process don't seem to work anymore
Issue Type: Bug
They still work fine in 1.30. I also checked the .scripts output and it looks like the sourcemap is getting used and the file mappings are correct, so I’m really unsure what is going on. I also verified the .scripts outputs the same in 1.30 as 1.31 and 1.30 works, but 1.31 doesn’t.
VS Code version: Code - Insiders 1.31.0-insider (5ab047b584d974033e0c5ce529ea74a869355b87, 2019-02-04T15:32:22.547Z) OS version: Windows_NT x64 10.0.18329
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i7-6700K CPU @ 4.00GHz (8 x 4008) |
| GPU Status | 2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 31.93GB (16.43GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 4
- Comments: 19 (15 by maintainers)
I can set them, they just show up as
unverifiedand won’t breakThere is an issue here: https://github.com/Microsoft/vscode-chrome-debug-core/issues/315
We are actually working on a large refactoring of the debug adapter which would fix this, but I have no idea when it will be ready.