23

In Qt Creator on Windows, qDebug() statements don't work, and the following message appears in the output window:

Cannot retrieve debugging output.

How can it be fixed?

sashoalm
  • 75,001
  • 122
  • 434
  • 781
laurent
  • 88,262
  • 77
  • 290
  • 428

5 Answers5

49

This problem can show up if more than one instance of Qt Creator is active. To fix the issue, simply close all the other instances of Qt Creator and it should work.

laurent
  • 88,262
  • 77
  • 290
  • 428
3

Or you may be running a version of DebugView from Sysinternals, that causes the same result.

Alex Strickland
  • 1,604
  • 1
  • 15
  • 13
3

For me, I solved the problem by simply closing the running application built with the other qt creator. So not necessary to close the other qt creator.

Xing Li
  • 46
  • 3
2

Well, I had two instances of QtCreator and I could not close one of them. They work together. One workaround for this problem is redirecting your application output messages using qInstallMessageHandler.

#include "mainwindow.h"

#include <QApplication>

void redirectedOutput(QtMsgType, const QMessageLogContext &, const QString &);
QMutex debugOutMutex;

int main(int argc, char *argv[])
{
    QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
    QApplication app(argc, argv);

    qInstallMessageHandler(redirectedOutput);
    
    MainWindow w;
    w.show();
    
    return app.exec();
}

void redirectedOutput(QtMsgType type, const QMessageLogContext &context, const QString &msg)
{
    debugOutMutex.lock();
    std::cout << QDateTime::currentDateTime().toString("hh.mm.ss.zzz  ").toStdString() <<  msg.toStdString() << std::endl;
    if (type == QtFatalMsg) {
        abort();
    }
    debugOutMutex.unlock();
}

I added a QMutex too. If your application is utilizing more than one thread, debug outputs can be mixed.

Mohammad Rahimi
  • 965
  • 5
  • 15
1

For me this error message appears when I have more than one instance of my application, not of Qt Creator.

Kévin Renella
  • 1,007
  • 9
  • 20