Bind stdin?

[duzenko]

How do I bind a file to standard input stream?

E.g. same as if I run from command line

myprogram.exe < stdin.txt

So that all reads from stdin actually read from that file rather than keyboard input.

[kensheldon]

@duzenko , would an exec-wrapper script suffice?
Your wrapper can modify the shell any way you like, as long as the last line is exec "$@"

Create the wrapper script:

#!/usr/bin/env bash
#
# a wrapper script to redirect stdin before running a command
#
exec 0< somefile.txt
exec "$@"

Then, add a startup command to your configuration

        {
            "type": "by-gdb",
            "request": "launch",
            "name": "blah blah blah",
            "program": "${workspaceRoot}/fee/fie/foe/fum",
            "cwd": "${workspaceRoot}/build/tests/fubar/",
            "programArgs": "yada yada yada",
            "preLaunchTask": "build target",
            "commandsBeforeExec": [
                "set exec-wrapper ${workspaceRoot}/utilities/wrapper.bash"
            ],
        }

[duzenko]

@kensheldon maybe I'm doing something wrong but for me it does not read from the stdin this way
See the attached

pasvsc.zip

[kensheldon]

If you're running on windows, you may need a different shell for your wrapper script. You could try CMD or PowerShell. I would expect git-bash would suffice, but maybe not.

The exec-wrapper functionality is a feature of GDB. You can test this directly in GDB, without VSCode. Build your program as usual, but then open your favorite shell (bash shell, cmd shell, powershell, etc), and use GDB to run the program. Once it works in GDB, you can figure out the proper launch configuration for vscode and beyond-gdb.

[duzenko]

I'd think an average user of vscode doesn't really use gdb directly and does not have experience with it - at least this is the case with me. If you don't have other suggestions then of course me neither.

[xuming]

You can write a pause in your program and run it .
After that, you can use "attach" to debug it .

[duzenko]

Sounds like a feature gap in your plugin really