Open lightmelodies opened 4 years ago
Type: Debugger
Describe the bug
command:pickProcess use ps axww -o pid=,comm=${PsProcessParser.commColumnTitle},args= to list running process. https://github.com/microsoft/vscode-cpptools/blob/dfca58c539aa399e145b6ad7ca3db546bcb077b9/Extension/src/Debugger/nativeAttach.ts#L117 It may lead your 131072x1 screen size is bogus, expect trouble error in remote wsl/ssh.
Similar issue: https://github.com/microsoft/vscode/issues/75932
Furthermore, if you have process with a long long command line, the ps output will lead to stdout maxBuffer exceeded error!
use ps axw -o pid=,comm=${PsProcessParser.commColumnTitle},args= 2>/dev/null will fix it.
Is there a workaround for this bug? I can't attach the debugger to a dotnet core process using Windows 10 WSL 2 + Ubuntu. I've tried using VS Code Insiders build to no avail.
Type: Debugger
Describe the bug
command:pickProcess use ps axww -o pid=,comm=${PsProcessParser.commColumnTitle},args= to list running process. https://github.com/microsoft/vscode-cpptools/blob/dfca58c539aa399e145b6ad7ca3db546bcb077b9/Extension/src/Debugger/nativeAttach.ts#L117 It may lead your 131072x1 screen size is bogus, expect trouble error in remote wsl/ssh.
Similar issue: https://github.com/microsoft/vscode/issues/75932
Furthermore, if you have process with a long long command line, the ps output will lead to stdout maxBuffer exceeded error!
use ps axw -o pid=,comm=${PsProcessParser.commColumnTitle},args= 2>/dev/null will fix it.