Important: Please read the Qt Code of Conduct -

GDB under QtCreator on WSL/Ubuntu 18.04 does not start properly

  • This happens when using QtCreator to debug a WSL program on Ubuntu 18.04: Start debugging, the program seems to start, GDB is launched, but either GDB doesn't seem to fully attach to the program, or QtCreator can't communicate with it. The QtCreator console is unable to interrupt the process. Quitting QtCreator leaves the debugger and the program hung.

    A simple console C++ application without Qt created by QtCreator's wizard for creating a new project demonstrates the issue.

    I've verified the same behavior on a number of different Windows 10 computers hosting WSL/Ubuntu 18.04. Windows is version 1909, WSL 1.

    The program can be debugged in a standalone GDB, or under Emacs GDB mode with no issues.


  • Lifetime Qt Champion

    @mlperini I would bring this to the developers mailing list or Qt Bug Tracker as I don't think many people use WSL already with Qt/QtCreator.

  • Hi,
    same here. I don't quit qtcreator, I hit Debug -> abort one or two times and after a few second a window appears saying that gdb is not responding and you have the possibility to click on a "stop debugging" button that works.
    I can see a message is the xterm where I launched qtcreator saying :

    "The command \"/mnt/c/Users/.../src\" could not be started."

    which is true since this is a directory. ;) May this wrong path is given to gdb instead of the path to the executable ?

  • @mlperini @jcm69 can you provide some steps to reproduce the issue with a minimal example?


    • how did you configure the kit for build/deployment?
    • are you running QtCreator on Windows or inside WSL through an Xserver?

Log in to reply