debug has no std output on the console

[dangbinghoo]

hi,

I just tried the debugger, it start's successfully, and support step execution very well. also I can see local vars. But I can't see the println 's output result.

so , what's the problem?

[YoshiWalsh]

I am seeing the same issue.

Here's my tasks.json:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "type": "cargo",
            "label": "cargo build",
            "command": "cargo",
            "args": [
                "build"
            ],
            "problemMatcher": [
                "$rustc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "presentation": {
                "echo": true,
                "reveal": "silent",
                "focus": false,
                "panel": "dedicated",
                "showReuseMessage": false
            }
        }
    ]
}

And here's my launch.json:

{
    // 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": [
        {
            "preLaunchTask": "cargo build",
            "name": "Debug",
            "type": "windbg",
            "request": "launch",
            "target": "./target/debug/rust-gol.exe",
            "verbosity": "debug",
            "windbgpath": "C:/Program Files (x86)/Windows Kits/10/Debuggers/x64/dbgeng.dll",
            "workingDir": "${workspaceRoot}",
            "sources": [
                "${workspaceRoot}/src"
            ]
        }
    ]
}

And my main.rs:

fn main() {
    println!("Hello, world!");
}

No stdout.

@dangbinghoo did you ever figure this out?

[michaelkonecny]

I have the same issue.

When I try to debug my binary directly using WinDbg, it opens up a separate console window where I can see the output. The same happens when I'm debugging in Visual Studio. However, in WinDbg-debug this doesn't happen.

Perhaps there is an option for WinDbg to open up a separate console window that just isn't being sent?

Any help would be appreciated, this is the only thing preventing me to finally ditch Visual Studio (the classic one) completely :-)