[Bug] Not able to attach to debugger in VS Code Terminal
KeyneZzz opened this issue · 3 comments
Version Information
Cmder version: Version 1.3.24.236
Operating system: Windows 11Cmder Edition
Cmder Full (with Git)
Description of the issue
I am using cmder in VSCode according to https://github.com/cmderdev/cmder/wiki/Seamless-VS-Code-Integration, and I want to attach to debugger when running some code on nodejs. But I found that I can only attach to vscode debugger on original CMD prompt.
How to reproduce
- in vscode, create a test.js file and add a console.log('foobar'), add breakpoint to this line
- toggle auto attach in any option other than "disabled"
- try run
node --inspect test.jsin vscode cmder terminal
expect: the execution will attach to vscode debugger, and will hit the breakpoint (what happened when using CMD prompt in vscode terminal)
current: not attached to debugger, the execution just finished
Additional context
No response
Checklist
- I have read the documentation.
- I have searched for similar issues and found none that describe my issue.
- I have reproduced the issue on the latest version of Cmder.
- I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.
update clink then resolved
I'm glad the issue went away.
How was Clink involved? This doesn't make any sense to me, as the author of Clink.
I'm glad the issue went away.
How was Clink involved? This doesn't make any sense to me, as the author of Clink.
In fact I was not expecting it to be resolved by updating clink, I just saw the clink update info, and wonder if making some change will make any change, so I update it and tried again, and find it work unexpectedly...