Qt Creator 14.0.2 buggy

king558

Hello Qt,

Currently I am using Qt Creator 14.0.2 and Qt Framework LTS 5.15.2, 6.5.3 and 6.8.0 with Visual Studio 2022, both x86 and x64 cdb are used. Source path mapping and cdb symbol path are used correctly, I regret to update to the latest version, last working version was still 11.03 of Qt Creator.

#include "mainwindow.h"
#include "ui_mainwindow.h"
#include <QDateTime>
#include <QUrl>

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
    , ui(new Ui::MainWindow)
{
    ui->setupUi(this);
    auto now = QDateTime::currentDateTime();
    auto tomorrow = now.addDays( 1 );
    auto url = QUrl( "https://abc.test.com/cdg/?pw:1234&language=english" );
    auto i = 0;
}

MainWindow::~MainWindow()
{
    delete ui;
}

As you can see screenshot 32 bit of 5.15.2, some variables are not accessible, url are cut until ? character

After switching to 64 bit of 5.15.2, 6.5.3 and 6.8.0, datetime variables are showing correctly, only url still cut out the half of url

Locals monitoring the variables are most import part during debugging, why is it so buggy? Is Qt Creator developed by part-time or hobby developer and there are no tester and QA for Qt Creator?

I also work for a company where these import part of a software getting so buggy, than that software wouldn't be roll out or employee would get fired.

Axel Spoerl

@king558 said in Qt Creator 14.0.2 buggy:

some variables are not accessible

i has been optimized out by the compiler. While it exists in the source, it's no longer present in the binary. Qt Creator knows that you might be expecting to see its value during debugging, and it shows you why that's not possible.

now is currently inaccessible, which means no memory has been allocated at the time of debugging. Usually that's because it's not yet or no longer needed.

Both are compiler features. Qt Creator (just like any other IDE) can only display in its debugging function, what the underlying debugger provides.

The implementation of QUrl provides a QDebug stream operator, which displays the URI-part of the class. The "?" separates this part from the parameters (in your case pw and language. The "Value" column is aiming at identifying the variable. While simple types like pointers (parent) or integers just hold one value that fits into the "Value" column, complex types like QUrl can be fully inspected by clicking on the little arrow. It will expand the class and expose everything you are looking for.

All of the above behaves exactly the same in Qt Creator 11 and 14. The reason why you may see different compiler / debugger optimizations is just different compilers and different architectures (32/64 bit).

@king558 said in Qt Creator 14.0.2 buggy:

Is Qt Creator developed by part-time or hobby developer

The larger parts of Qt Creator are developed by highly skilled professionals employed by the Qt Company.
However, it's an open source product and many members of the open source community also contribute to Qt Creator on a voluntary basis. They usually are just as skilled as my colleagues.

@king558 said in Qt Creator 14.0.2 buggy:

there are no tester and QA for Qt Creator?

Of course Qt Creator is properly tested. That's why it's so good.

@king558 said in Qt Creator 14.0.2 buggy:

employee would get fired.

Either you need a new job, or an attitude adjustment ;-)

king558

@Axel-Spoerl said in Qt Creator 14.0.2 buggy:

@king558 said in Qt Creator 14.0.2 buggy:

some variables are not accessible

i has been optimized out by the compiler. While it exists in the source, it's no longer present in the binary. Qt Creator knows that you might be expecting to see its value during debugging, and it shows you why that's not possible.

now is currently inaccessible, which means no memory has been allocated at the time of debugging. Usually that's because it's not yet or no longer needed.

Both are compiler features. Qt Creator (just like any other IDE) can only display in its debugging function, what the underlying debugger provides.

The implementation of QUrl provides a QDebug stream operator, which displays the URI-part of the class. The "?" separates this part from the parameters (in your case pw and language. The "Value" column is aiming at identifying the variable. While simple types like pointers (parent) or integers just hold one value that fits into the "Value" column, complex types like QUrl can be fully inspected by clicking on the little arrow. It will expand the class and expose everything you are looking for.

All of the above behaves exactly the same in Qt Creator 11 and 14. The reason why you may see different compiler / debugger optimizations is just different compilers and different architectures (32/64 bit).

@king558 said in Qt Creator 14.0.2 buggy:

Is Qt Creator developed by part-time or hobby developer

The larger parts of Qt Creator are developed by highly skilled professionals employed by the Qt Company.
However, it's an open source product and many members of the open source community also contribute to Qt Creator on a voluntary basis. They usually are just as skilled as my colleagues.

@king558 said in Qt Creator 14.0.2 buggy:

there are no tester and QA for Qt Creator?

Of course Qt Creator is properly tested. That's why it's so good.

@king558 said in Qt Creator 14.0.2 buggy:

employee would get fired.

Either you need a new job, or an attitude adjustment ;-)

First of all, thx you for you responding. I am using Qt since 2016, the quality of Qt Creator has significatly dropped since Version 12. I have both version Qt Creator 11.0.3 and 14.0.2 installed. 11.0.3 is still working, but 14 version most defected version. My expression is, that Qt Creator roll out focus on feature not on stablity of whole IDE. I also heard from other Qt Senior Developer, that they do not use the most recently version of Qt Creator, because it consider as Alpha or Beta Version.

Axel Spoerl

@king558 said in Qt Creator 14.0.2 buggy:

the quality of Qt Creator has significatly dropped since Version 12

None of the issues mentioned in this post are even remotely related to Qt Creator.
If something else got broken in Qt Creator, say exactly what it is and we'll fix it.
I'll put it the other way round: The quality of Qt Creator has significantly improved with every version. I use QtC 14 as my daily working horse and it works like a charm. If you think I am wrong, prove it :-)

@king558 said in Qt Creator 14.0.2 buggy:

I also heard from other Qt Senior Developer, that they do not use the most recently version of Qt Creator, because it consider as Alpha or Beta Version.

The most important issue with QtC 14 is that support for 32bit builds has been dropped. Some people might stick to older versions because of that. The rest is hearsay.

king558

@Axel-Spoerl said in Qt Creator 14.0.2 buggy:

@king558 said in Qt Creator 14.0.2 buggy:

the quality of Qt Creator has significatly dropped since Version 12

None of the issues mentioned in this post are even remotely related to Qt Creator.
If something else got broken in Qt Creator, say exactly what it is and we'll fix it.
I'll put it the other way round: The quality of Qt Creator has significantly improved with every version. I use QtC 14 as my daily working horse and it works like a charm. If you think I am wrong, prove it :-)

@king558 said in Qt Creator 14.0.2 buggy:

I also heard from other Qt Senior Developer, that they do not use the most recently version of Qt Creator, because it consider as Alpha or Beta Version.

The most important issue with QtC 14 is that support for 32bit builds has been dropped. Some people might stick to older versions because of that. The rest is hearsay.

I just read this topic, it also from you.

If that the case, than the recently online installer should not list MingGW 8 anymore.

Are you also using multiple Version Qt Version at same time and 32 bit and 64 bit, Visual Studio and MingW, it is definedly not tested on all compiler, if that the case, online installer should also drop the installation of Mingw 8 32 bit. Early my colluege also found an error in Qt source earlier, he has fix it before Qt do. You can beleave me, there are outside Qt guru.

king558

@Axel-Spoerl said in Qt Creator 14.0.2 buggy:

@king558 said in Qt Creator 14.0.2 buggy:

the quality of Qt Creator has significatly dropped since Version 12

None of the issues mentioned in this post are even remotely related to Qt Creator.
If something else got broken in Qt Creator, say exactly what it is and we'll fix it.
I'll put it the other way round: The quality of Qt Creator has significantly improved with every version. I use QtC 14 as my daily working horse and it works like a charm. If you think I am wrong, prove it :-)

@king558 said in Qt Creator 14.0.2 buggy:

I also heard from other Qt Senior Developer, that they do not use the most recently version of Qt Creator, because it consider as Alpha or Beta Version.

The most important issue with QtC 14 is that support for 32bit builds has been dropped. Some people might stick to older versions because of that. The rest is hearsay.

I thank you for you responding, but what I means, In our company we have much more strict rules in QA. We would get fired if obviously mistake get through. I do not means developer in Qt. I personally like Qt Framework and appreciate your work. But I hope there are more impovement in the online installer.

Axel Spoerl

You haven’t provided a single example of a mistake in Qt Creator. You just claim that it has mistakes without any proof. Same for the online installer, that you mentioned now.

Then you conclude, again without any proof, that „your company“ has stricter QA than Qt.

All of these statements are untrue.