How to pass command-line arguments to debugger using VSCode?

Question

I'm using VSCode on Linux and I've came up with a the following launch configuration in my attempt to fire the VSCode debugger, which, in turn, would rely on gdb:

{
    "version": "0.2.0",
    "configurations": [
    {
        "name": "(gdb) Launch",
        "type": "cppdbg",
        "request": "launch",
        "program": "${fileDirname}/${fileBasenameNoExtension}",
        "args": ["a", "b", "c", "d", "e"],
        "stopAtEntry": false,
        "cwd": "${fileDirname}",
        "environment": [],
        "externalConsole": false,
        "MIMode": "gdb",
        "setupCommands": [
            {
                "description": "Enable pretty-printing for gdb",
                "text": "-enable-pretty-printing",
                "ignoreFailures": true
            }
        ],
        "preLaunchTask": "make project"
    }]

}

Here, using the args attribute I'd like to pass 5 arguments to the process I'm debugging, namely: "a", "b", "c", "d", "e".

However, when I run the debugger, the argc value is correctly set to 6, but the values themselves, stored by argv are not present.

same problem，I also have a question in stackoverflow.com/questions/60415097/… — weichao
– weichao, Commented Feb 26, 2020 at 13:42
Do you have a solution for it? I have been stuck in there for a while :( — weichao
– weichao, Commented Feb 26, 2020 at 13:43

Trass3r · Accepted Answer · 2020-10-04 04:05:13Z

3

That's cause the type of argv is char**. The debugger doesn't know if it's pointing at a single element or an array.

In VS you can use format specifiers. With gdb you should be able to use something like this in the Watch view:

(char*[6])argv

https://github.com/Microsoft/vscode-cpptools/issues/688#issuecomment-685956825

answered Oct 4, 2020 at 4:05

Trass3r

6,3672 gold badges33 silver badges50 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

bazz-dee · Accepted Answer · 2019-12-19 09:19:01Z

2

The first argument is always the executable. This is expected behaviour.

answered Dec 19, 2019 at 9:19

bazz-dee

6976 silver badges23 bronze badges

Collectives™ on Stack Overflow

How to pass command-line arguments to debugger using VSCode?

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related