Qt creator no qDebug() output in debug mode - Qt 6.10.2

JonB

@MHMart_asc , @aha_1980
I am not a Windows/MSVC user. But if this (presently?) does not work for MSVC/cdb does installing and running DebugView allow you to see debug output?

J.Hilk

stupid question but, is your cmake configuration on debug as well? I would assume so, but double checking won't hurt

MHMart_asc

@J.Hilk said in Qt creator no qDebug() output in debug mode - Qt 6.10.2:

stupid question but, is your cmake configuration on debug as well? I would assume so, but double checking won't hurt

Probably the solution will be even more stupid considering I am the one with the issue :)

Can you tell me how to check that?

@JonB said in Qt creator no qDebug() output in debug mode - Qt 6.10.2:

@MHMart_asc , @aha_1980
I am not a Windows/MSVC user. But if this (presently?) does not work for MSVC/cdb does installing and running DebugView allow you to see debug output?

[19144] Error: Change all symbol paths attempts to access '""' failed: 0x7b - De syntaxis van de bestandsnaam, mapnaam of volumenaam is onjuist.
[19144] 
[19144] ************* Path validation summary **************
[19144] Response                         Time (ms)     Location
[19144] Error                                         
[19144]  
[19144] ""
[19144] 
[3228] Suspending

JonB

@MHMart_asc
So your screenshot shows all output sent to debug on your system. I don't know whether the PIDs shown are for your Qt program or not, only you do. Whether this will work for them or not depends on how the qDebug() output is sent and whatever the nature of the reported "bug" is.

If you really need qDebug() output and cannot wait while some bug gets fixed, install a qInstallMessageHandler() and redirect its output from there to whatever suits, e.g. for the DebugView it would be Windows OutputDebugString().

J.Hilk

@MHMart_asc said in Qt creator no qDebug() output in debug mode - Qt 6.10.2:

Can you tell me how to check that?

go to your project tab and check the CMAKE_BUILD_TYPE variable

initial config and current

cristian-adam

@aha_1980 said in Qt creator no qDebug() output in debug mode - Qt 6.10.2:

@MHMart_asc: Looks like QTCREATORBUG-33741.

So for LLDB there is a bugfix in 19.0, but for cdb it seems there is currently no fix available.

At QTCREATORBUG-33741 we have:

cdb:

when launching without terminal, the qDebug output is not shown in the "Application Output" pane

when "Run in terminal" is enabled, the qDebug output is shown in the terminal

lldb:

when launching without terminal, the qDebug output is not shown in the "Application Output" pane

when "Run in terminal" is enabled, the qDebug output is not shown in the terminal, either

With Qt Creator 18.0.2 and cdb all that @MHMart_asc needs to do is set the checkbox Run in terminal for the project.

For Qt Creator 19 I've made sure that lldb would work when Run in terminal is set.

MHMart_asc

@cristian-adam said in Qt creator no qDebug() output in debug mode - Qt 6.10.2:

With Qt Creator 18.0.2 and cdb all that @MHMart_asc needs to do is set the checkbox Run in terminal for the project.

That causes the following error:

cristian-adam

@MHMart_asc You could try disabling the QML Debugger.

MHMart_asc

@cristian-adam I do now get an output in the terminal, So at least that's that. thank you.

Exception at 0x7ff9e7ffa80a, code: 0xe06d7363: C++ exception, flags=0x81 (first chance) in DWrite

Exception at 0x7ff9e7ffa80a, code: 0xe06d7363: C++ exception, flags=0x81 (first chance) in DWrite

Exception at 0x7ff9e7ffa80a, code: 0xe06d7363: C++ exception, flags=0x81 (first chance) in DWrite

Exception at 0x7ff9e7ffa80a, code: 0xe06d7363: C++ exception, flags=0x81 (first chance) in DWrite

Still I get these exceptions in the application output. Is that relevant?

JonB

@MHMart_asc No, always ignore "first chance exceptions" when debugging under Windows.