NSight VSCE Remote debugging: No stdout on debug console

I managed setting up the nsight visual studio code edition for remote debugging.
With this launch.json file:

    "configurations": [
            "name": "CUDA C++ Launch",
            "type": "cuda-gdb",
            "request": "launch",
            "program": <path to executable>,
            "arguments": <Arguments>,
            "externalConsole": false
The debug environment works well and tracks variables etc.
But the debug console omits any stdout data.
This is the debug console output:
NVIDIA (R) CUDA Debugger 10.2 release Portions Copyright (C) 2007-2019 NVIDIA Corporation

GNU gdb (GDB) 7.12

Copyright (C) 2016 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details.

This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see:


Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".

Type "apropos word" to search for commands related to "word".

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".


warning: Cannot parse .gnu_debugdata section; LZMA support was disabled at compile time

Breakpoint 1, main (argc=15, argv=0x7fffffffe408) at src/main.cu:77

77 Config config = parseArgs(argc, argv);

Breakpoint 3, main (argc=15, argv=0x7fffffffe408) at src/main.cu:134

134 if (config.sortEdges)

There was supposed to be some printf() output text in between breakpoint 1 and 3 but it wasn't shown at all.

Just to double-check, did you mean to say remote debugging? It doesn’t look like your configuration would support remote debugging but I may be missing some details. If you are remote debugging, do you only see this issue in remote debugging or also local debugging?

By remote debugging, I meant on a server connected via ssh. This totally works existing configuration. (I am using the Nvidia Visual Studio Code Extension).
I don’t have local machine that I can plug in to for trying this out.

We aren’t seeing this reproduce. Two questions:

  1. Have you tried with a newer version of CUDA than 10.2?
  2. Is there a specific CUDA sample you can reproduce this with that we can try?