Debugger Breakpoints not being honored #236107
Assignees
Labels
info-needed
Issue requires more information from poster
Comments
|
/jsDebugLogs |
|
Please collect trace logs using the following instructions:
|
|
Please use an older version of Node.js nodejs/node#56002 |
|
Thank you Connor, this fixed the issue!
Brendan Rooney
Senior Software Engineer
***@***.***
1765 N. Elston Ave.
Chicago, IL 60642
O: (312) 698-8485
***@***.***
***@***.******@***.******@***.******@***.***<https://twitter.com/redwoodlgistics>
***@***.***<https://t.xink.io/Tracking/Index/-WwCAIurAQDdvcoA0>
From: Connor Peet ***@***.***>
Sent: Friday, December 13, 2024 10:10 PM
To: microsoft/vscode ***@***.***>
Cc: Rooney, Brendan ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/vscode] Debugger Breakpoints not being honored (Issue #236107)
[EXTERNAL EMAIL]
Please use an older version of Node.js nodejs/node#56002<nodejs/node#56002>
—
Reply to this email directly, view it on GitHub<#236107 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHC4J6JNOAASSNJZ25ZO5MD2FOVQVAVCNFSM6AAAAABTSZA6P2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBSG43TMNBTG4>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type: Bug
The Microsoft VSCode Debugger is not honoring the breakpoints or debugger lines when attempting to debug a javascript file. The debugger skips past the breakpoints and debugger lines and simply runs the entire file.
I tried these same configs on other computers and they worked without issue. I have since restarted my computer several times. I have also installed VSCode Insiders, which would be a fresh install, and saw the issue happening there as well. I created a new npm project and attempted to debug the most basic js file there and also saw same issues. Stack overflow, ChatGPT and Co-Pilot all gave many recommendations to try which all resulted in similar results. The only thing that seems to be working is when debugging in chrome dev tools via a web-sockets connection.
An example of the output that is sent to the VSCode integrated terminal when debugging is below. The below ran with the trace option turned on for extra logs. You can see the last portion says 'This is a Test', which is a console statement at the end of the file attempting to be debugged.
cd c:\Users\brooney\Downloads\debugIssue ; /usr/bin/env 'NODE_OPTIONS= --require "c:/Users/brooney/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.js" --inspect-publish-uid=http' 'VSCODE_INSPECTOR_OPTIONS=:::{"inspectorIpc":"\\.\pipe\node-cdp.27104-a52099ff-9.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\Program Files\nodejs\node.exe","onlyEntrypoint":false,"verbose":true,"autoAttachMode":"always","fileCallback":"C:\Users\brooney\AppData\Local\Temp\node-debug-callback-d776087ff7bce7f1"}' C:\Program\ Files\nodejs\node.exe .\debug.js
s","fileCallback":"C:\\Users\\brooney\\AppData\\Local\\Temp\\node-debug-callback-d776087ff7bce7f1"}' C:\\Program\ Files\\nodejs\\node.exe .\\debug.js ;fa763c12-ed8e-4e84-89da-e434e8b3a536runtime.launch Bootloader imported {
env: {
inspectorIpc: '\\.\pipe\node-cdp.27104-a52099ff-9.sock',
deferredMode: false,
waitForDebugger: '',
execPath: 'C:\Program Files\nodejs\node.exe',
onlyEntrypoint: false,
verbose: true,
autoAttachMode: 'always',
fileCallback: 'C:\Users\brooney\AppData\Local\Temp\node-debug-callback-d776087ff7bce7f1'
},
args: [
'C:\Program Files\nodejs\node.exe',
'C:\Users\brooney\Downloads\debugIssue\debug.js'
]
}
runtime Set debug mode { mode: 2 }
This is a test
VS Code version: Code 1.96.0 (138f619, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
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_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (31)
A/B Experiments
The text was updated successfully, but these errors were encountered: