microsoft / microsoft/vscode-cpptools

Cannot change the default input stream on debug.

Open
#2,329 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

This is my configuration for the launch.json file:

{
    "name": "(gdb) Launch",
    "type": "cppdbg",
    "request": "launch",
    "program": "${workspaceFolder}/a.exe",
    "args": ["<", "input.txt"],
    "stopAtEntry": false,
    "cwd": "${workspaceFolder}",
    "environment": [
        {"name": "OUTPUT_PATH", "value": "results.txt"}
    ],
    "externalConsole": false,
    "MIMode": "gdb",
    "miDebuggerPath": "C:/cygwin64/bin/gdb.exe",
    "preLaunchTask": "build",
    "setupCommands": [
        {
            "description": "Enable pretty-printing for gdb",
            "text": "-enable-pretty-printing",
            "ignoreFailures": true
        }
    ]
}

Using this:

"args": ["<", "input.txt"]

I wanted to redirect the default input stream to read from the file "input.txt" but this does not work.

Is there any hack around it or it's just a feature that the extension doesn't yet have?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the launch.json configuration and trace how the cppdbg launch request passes its args to gdb, especially when using Cygwin. Reproduce the configuration with input.txt and compare the extension's handling of arguments with the requested default-input behavior. Done means a documented or implemented way to use input.txt as the debugged program's standard input.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.