Macbook M1 - debugger, scanf does not read from console

[mosmar99]

Bug type: Debugger

Describe the bug

• OS and Version: Monterey
• VS Code Version: Insiders edition
• C/C++ Extension Version: 1.93
• Other extensions you installed (and if the issue persists after disabling them): C/C++ debug extension
• A clear and concise description of what the bug is. I can't read from standard input, i.e. terminal. In addition, I can't get the debugger working for C with an external terminal. It opens two terminals which are disconnected from the debugging process. When I do enter, say an integer, into the terminal, I just get the error: "Unable to perform this action because the process is running." Which I presume is due to standard input being disconnected from the debugger and the file as a whole, more or less.

To Reproduce
Please include a code sample and launch.json configuration.

Launch:
{ // 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": [ { "name": "(lldb) Launch", "type": "cppdbg", "request": "launch", "targetArchitecture": "x86_64", "program": "${workspaceFolder}/${fileBasenameNoExtension}.x86_64", "args": [], "stopAtEntry": true, "cwd": "${fileDirname}", "environment": [], "externalConsole": false, "osx": { "preLaunchTask": "build (x86_64)", "MIMode": "lldb" } } ] }

Tasks:
{ // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format "version": "2.0.0", "tasks": [ { "label": "build (x86_64)", "type": "shell", "command": "clang", "args": [ "-arch", "x86_64", "-g", "-o", "${workspaceFolder}/${fileBasenameNoExtension}.x86_64", "${fileDirname}/${fileBasename}" ], "group": "build" }, { "label": "build (arm64)", "type": "shell", "command": "clang", "args": [ "-arch", "arm64", "-g", "-o", "${workspaceFolder}/${fileBasenameNoExtension}.arm64", "${fileDirname}/${fileBasename}" ], "group": "build" }, { "label": "build (Mach-O Universal)", "type": "shell", "command": "lipo", "dependsOn":["build (x86_64)", "build (arm64)"], "args": [ "-create", "-output", "${workspaceFolder}/${fileBasenameNoExtension}", "${workspaceFolder}/${fileBasenameNoExtension}.x86_64", "${workspaceFolder}/${fileBasenameNoExtension}.arm64" ], "group": { "kind": "build", "isDefault": true } } ] }

Create a new c file, test.c.
Try running the code:
`#include <stdio.h>

int main(void) {
int test;
printf("hello");
scanf("%d", &test);
return 0;
}`

As a computer science student debugging is of vital importance for more or less all of my assignments. Solving this issue would heavily facilitate my workflow.
Thanks in advance.

[WardenGnaw]

You will want to switch externalConsole: false to be true so you can interact with the terminal to write to it.

Integrated terminal is not supported for lldb: #6715

[mosmar99]

You will want to switch externalConsole: false to be true so you can interact with the terminal to write to it.

Integrated terminal is not supported for lldb: #6715

Thank you for your reply Warden. Although, it doesn't really solve the issue for me. When I choose to have an external console, it pops up 2 external terminal windows which are seemingly completely disconnected from my debugging process. Check out the picture below for reference:

By the way, upon debugging I gather this error message: > Executing task: clang -arch x86_64 -g -o /Users/mahmut/Desktop/c/datastrukturer/tasks/graphs/launch.x86_64 /Users/mahmut/Desktop/c/datastrukturer/tasks/graphs/.vscode/launch.json <

ld: warning: ignoring file /Users/mahmut/Desktop/c/datastrukturer/tasks/graphs/.vscode/launch.json, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x7B 0x0A 0x20 0x20 0x20 0x20 0x2F 0x2F 0x20 0x55 0x73 0x65 0x20 0x49 0x6E 0x74 )
Undefined symbols for architecture x86_64:
"_main", referenced from:
implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The terminal process "/bin/zsh '-c', 'clang -arch x86_64 -g -o /Users/mahmut/Desktop/c/datastrukturer/tasks/graphs/launch.x86_64 /Users/mahmut/Desktop/c/datastrukturer/tasks/graphs/.vscode/launch.json'" failed to launch (exit code: 1).

Thank you in advance.

[WardenGnaw]

The logs seem to be from the complier.

The window that is currently on top in your image is the one spawned for external console input.
The three messages on top are from lldb.

[mosmar99]

The logs seem to be from the complier.

The window that is currently on top in your image is the one spawned for external console input. The three messages on top are from lldb.

Current output:

What you are saying might very well be accurate. The problem stands that my debugging tools, such as the keyboard keys F10 and F11 are disconnected from the terminal that pops up. Same is true for the mouse-clickable arrows. There is no "yellow line" highlighter to specify "current line".

At least, setting the external console to false gets me the yellow line-highlighter as well as blue-highlighted output in the debug-console output. The only problem is that I can not read from it.

[StefanoD]

Same problem here. :-(

[Oureyelet]

I have still same problem

[Adelesnoko]

Go to Settings - Search for Terminal - drop down the menu and look for "Code-runner: Run In Terminal", and check the box.

Solution from: How to give input in VS Code || Cannot edit in read only mode || Running Code in terminal in VSCode

[eljugador003]

The solution given above me, does not solve the issue, I am one of those people with the same issue

[flawesomesoft]

@eljugador003
None of the mentioned solutions worked for me as well.
I only got it to work using CodeLLDB extension.

In Debugger section click on "Add Configuration..." and select "LLDB" in the list. It should look something like this:

//launchsettings.json
{
    
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug lldb",
            "program": "${workspaceFolder}/${fileBasenameNoExtension}",
            "args": [],
            "cwd": "${workspaceFolder}",
        }
    ]
}

For tasks.json i used the auto-generated one via clang which you will be prompted when running the program for the first time. It should look like that:

// tasks.json
{
    "tasks": [
        {
            "type": "cppbuild",
            "label": "C/C++: clang build active file",
            "command": "/usr/bin/clang",
            "args": [
                "-fcolor-diagnostics",
                "-fansi-escape-codes",
                "-g",
                "${file}",
                "-o",
                "${fileDirname}/${fileBasenameNoExtension}"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ],
    "version": "2.0.0"
}

With this configuration in place you will be no longer debugging in the faulty "Debugger Console". Instead you're debugging in the Terminal.

Hope this solution works.

#Unable to perform this action because the process is running. #1027

[MoodyRoyce]

for me it worked before but the problem is somehow there since I downloaded android studio and dart. Is it the case for anyone else ?

[Okywan]

@eljugador003 None of the mentioned solutions worked for me as well. I only got it to work using CodeLLDB extension.

In Debugger section click on "Add Configuration..." and select "LLDB" in the list. It should look something like this:

//launchsettings.json
{
    
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug lldb",
            "program": "${workspaceFolder}/${fileBasenameNoExtension}",
            "args": [],
            "cwd": "${workspaceFolder}",
        }
    ]
}

For tasks.json i used the auto-generated one via clang which you will be prompted when running the program for the first time. It should look like that:

// tasks.json
{
    "tasks": [
        {
            "type": "cppbuild",
            "label": "C/C++: clang build active file",
            "command": "/usr/bin/clang",
            "args": [
                "-fcolor-diagnostics",
                "-fansi-escape-codes",
                "-g",
                "${file}",
                "-o",
                "${fileDirname}/${fileBasenameNoExtension}"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ],
    "version": "2.0.0"
}

With this configuration in place you will be no longer debugging in the faulty "Debugger Console". Instead you're debugging in the Terminal.

Hope this solution works.

#Unable to perform this action because the process is running. #1027

This worked for me on macOS Sonoma with M1 Pro.