vscode-bash-debug icon indicating copy to clipboard operation
vscode-bash-debug copied to clipboard

No Debug Terminal appears when starting debug

Open ivavid opened this issue 3 years ago • 2 comments

Executables

Bash debug: 0.3.9 vscode: 1.65-insider OS: Windows 10

PS C:\Users\user123> where bash
PS C:\Users\user123> # if `code` not found on macOS, follow the instructions in:
PS C:\Users\user123> # https://code.visualstudio.com/docs/setup/mac
PS C:\Users\user123> code --version
code: The term 'code' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
PS C:\Users\user123> bash -c 'uname -a; for P in bash bashdb cat mkfifo pkill; do echo ---; which -a $P; command $P --version; done'
Linux MMO-TO6735-1 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
---
/usr/bin/bash
/bin/bash
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
---
/bin/bash: bashdb: command not found
---
/usr/bin/cat
/bin/cat
cat (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Torbjorn Granlund and Richard M. Stallman.
---
/usr/bin/mkfifo
/bin/mkfifo
mkfifo (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.
---
/usr/bin/pkill
/bin/pkill
pkill from procps-ng 3.3.16

Debug output

No debug output. My launch.json is as follows:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "bashdb",
            "request": "launch",
            "name": "Bash-Debug",
            "cwd": "${workspaceFolder}",
            "program": "${file}",
            "args": [],
            "showDebugOutput": true,
            "trace": true
        }
    ]
}

Details

Debugging the following program opens no Debug Console terminal and renders no output in any terminal, as in the example gif. There is output in the Debug Console, but entering a number there for the program to read does nothing.

#!/bin/bash

echo "Enter a number."
read -r number

I've tried setting the attribute console to the different settings as listed on the vscode Debug page, to no avail.

Expected behaviour: The Debug Console terminal appears as in the example gif, and output and input from the debugged program appears there.

ivavid avatar Feb 11 '22 12:02 ivavid