Re: [Development] Qt 5.12 and debug/warnings messages
On Fri, 11 Jan 2019 at 19:03, Fabrice Mousset | GEOCEPT GmbH wrote: > > Hi Kai, > > I've used the development mailing list because I think this is a bug in the > release. > When I build my application with Qt 5.4.2, Qt 5.6.x or Qt 5.11.2 all works as > expected. > But with Qt 5.12.0, nothing works. Only qCritical() messages are working. > > To be more explicit, I use qInstallMessageHandler() to register my logger > callback function. > The callback method is only called (with Qt 5.12.0) when qCritical() is > used. qDebug() and qWarning() have no effect! > So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been build > with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT. > Once again, with previous Qt release, all works as expected. > > Regards > > Fabrice Hi Fabrice, I'm on Windows 10 64-bit, using the official pre-built version of Qt 5.12.0 for MSVC 2017 32-bit. I can confirm that qDebug() and co are working as usual for me, so I don't think there is anything wrong with Qt 5.12.0 itself. So, let's figure out why it's not working on your machine. First, can you provide details on how you installed this version of Qt 5.12.0? Second, launch SysInternals DebugView (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview ) before you launch Qt Creator. Do your qDebug() messages appear in DebugView? Regards, Sze-Howe > -Ursprüngliche Nachricht- > Von: Kai Koehne > Gesendet: Freitag, 11. Januar 2019 10:34 > An: Fabrice Mousset | GEOCEPT GmbH ; > development@qt-project.org > Betreff: RE: Qt 5.12 and debug/warnings messages > > Hi Fabrice, > > There's been no such change. Your problem is most likely one of two: > > - You actually disable the qDebug, qWarning via custom logging rules. See > http://doc.qt.io/qt-5/qloggingcategory.html , section "Logging Rules" for the > details. > > - You have a GUI program that logs to the system wide debugging log, but > other IDE's or debuggers are interfering. Make sure that you don't run > multiple IDE's or debuggers at the same time. > > In general, this is the wrong mailing list for questions about Qt itself. > Please contact either support (if you're a commercial customer), or use the > forums or inter...@qt-project.org. > > Regards > > Kai > > > -Original Message- > > From: Development On Behalf Of > > Fabrice Mousset | GEOCEPT GmbH > > Sent: Friday, January 11, 2019 9:50 AM > > To: development@qt-project.org > > Subject: [Development] Qt 5.12 and debug/warnings messages > > > > Hi, > > > > > > > > I have installed Qt 5.12.0 for Windows / MSVC2017-32bit with Qt > > Maintenance Tool. > > > > I wondering why qDebug and qWarning have been disabled in this version? > > > > qDebug() and qWarning() do not work, even in Debug build! Why? > > > > Is this intentional? > > > > > > > > Do I have to build Qt from sources to made them work again or will > > this be fixed/changed in next build (Qt 5.12.1)? > > > > > > > > Regards > > > > > > > > Fabrice Mousset ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 5.12 and debug/warnings messages
Kai Koehne (11 January 2019 10:33) wrote > There's been no such change. Your problem is most likely one of two: > > - You actually disable the qDebug, qWarning via custom logging > rules. See http://doc.qt.io/qt-5/qloggingcategory.html , section > "Logging Rules" for the details. Note that this might not be "You" so much as your O/S: I've had a Debian system provide its own /etc/xdg/QtProject/qtlogging.ini by default, that blocked my attempts to see QDebug and QWarning output. I duly over-rode it with an empty ~/.sys/config/QtProject/qtlogging.ini (well, empty aside from a comment telling me why it was there). The system-wide one seems to have gone away, on Debian/testing, but it might still be there on older versions or other systems. Eddy. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 5.12 and debug/warnings messages
Hi Kai,
the example is very simple:
-8<-- DebugTest.pro
QT -= gui
CONFIG += c++11 console
CONFIG -= app_bundle
SOURCES += main.cpp
---
-8<-- main.cpp ---
#include
#include
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
qDebug() << "Hello Debug";
qWarning() << "Hello Warning";
qCritical() << "Hello Critical";
//return a.exec();
return 0;
}
When build and run with 5.4.2, output is
Hello Debug
Hello Warning
Hello Critical
When build and run with 5.4.2, output is
Hello Critical
That's it!
-Ursprüngliche Nachricht-
Von: Kai Koehne
Gesendet: Freitag, 11. Januar 2019 11:00
An: Fabrice Mousset | GEOCEPT GmbH ;
development@qt-project.org
Betreff: RE: Qt 5.12 and debug/warnings messages
> -Original Message-
> [...]
> So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been
> build with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT.
That's not the case, at least for the official packages. QT_NO_WARNING_OUTPUT,
QT_NO_DEBUG_OUTPUT anyway does only affect the code it was compiled with. That
is, qDebug() in your own code shouldn't be affected if Qt itself was compiled
with QT_NO_XXX_OUTPUT.
> Once again, with previous Qt release, all works as expected.
Please try to create a minimal example, and add it to a Qt Support or
bugtracker ticket.
Regards
Kai
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 5.12 and debug/warnings messages
> -Original Message- > [...] > So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been build > with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT. That's not the case, at least for the official packages. QT_NO_WARNING_OUTPUT, QT_NO_DEBUG_OUTPUT anyway does only affect the code it was compiled with. That is, qDebug() in your own code shouldn't be affected if Qt itself was compiled with QT_NO_XXX_OUTPUT. > Once again, with previous Qt release, all works as expected. Please try to create a minimal example, and add it to a Qt Support or bugtracker ticket. Regards Kai ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 5.12 and debug/warnings messages
Hi Kai, I've used the development mailing list because I think this is a bug in the release. When I build my application with Qt 5.4.2, Qt 5.6.x or Qt 5.11.2 all works as expected. But with Qt 5.12.0, nothing works. Only qCritical() messages are working. To be more explicit, I use qInstallMessageHandler() to register my logger callback function. The callback method is only called (with Qt 5.12.0) when qCritical() is used. qDebug() and qWarning() have no effect! So I've supposed the Qt 5.12.0 release (MSVC2017 / 32bit) have been build with QT_NO_WARNING_OUTPUT and QT_NO_DEBUG_OUTPUT. Once again, with previous Qt release, all works as expected. Regards Fabrice -Ursprüngliche Nachricht- Von: Kai Koehne Gesendet: Freitag, 11. Januar 2019 10:34 An: Fabrice Mousset | GEOCEPT GmbH ; development@qt-project.org Betreff: RE: Qt 5.12 and debug/warnings messages Hi Fabrice, There's been no such change. Your problem is most likely one of two: - You actually disable the qDebug, qWarning via custom logging rules. See http://doc.qt.io/qt-5/qloggingcategory.html , section "Logging Rules" for the details. - You have a GUI program that logs to the system wide debugging log, but other IDE's or debuggers are interfering. Make sure that you don't run multiple IDE's or debuggers at the same time. In general, this is the wrong mailing list for questions about Qt itself. Please contact either support (if you're a commercial customer), or use the forums or inter...@qt-project.org. Regards Kai > -Original Message- > From: Development On Behalf Of > Fabrice Mousset | GEOCEPT GmbH > Sent: Friday, January 11, 2019 9:50 AM > To: development@qt-project.org > Subject: [Development] Qt 5.12 and debug/warnings messages > > Hi, > > > > I have installed Qt 5.12.0 for Windows / MSVC2017-32bit with Qt > Maintenance Tool. > > I wondering why qDebug and qWarning have been disabled in this version? > > qDebug() and qWarning() do not work, even in Debug build! Why? > > Is this intentional? > > > > Do I have to build Qt from sources to made them work again or will > this be fixed/changed in next build (Qt 5.12.1)? > > > > Regards > > > > Fabrice Mousset ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt 5.12 and debug/warnings messages
Hi, I have installed Qt 5.12.0 for Windows / MSVC2017-32bit with Qt Maintenance Tool. I wondering why qDebug and qWarning have been disabled in this version? qDebug() and qWarning() do not work, even in Debug build! Why? Is this intentional? Do I have to build Qt from sources to made them work again or will this be fixed/changed in next build (Qt 5.12.1)? Regards Fabrice Mousset ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
