Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-89678

Function crashes as soon as a QVariant is create with -fstack-protector on

    XMLWordPrintable

Details

    • Bug
    • Resolution: Out of scope
    • P1: Critical
    • None
    • 6.0.0
    • Core: Containers and Algorithms
    • None
    • Windows

    Description

      1. Have a Qt 6.0.0 with GCC 8.1.0 on Windows (should also work on Linux). This is a 6.0.0 regression, with Qt 5.15 it works fine.
      2. Compile the following program:
      #include <QCoreApplication>
#include <QTimer>
#include <QVariant>

void setCursor() {
    QVariant(1);
}

int main(int argc, char *argv[])
{
    QCoreApplication a(argc, argv);

    setCursor();

    QTimer::singleShot(0, &a, &QCoreApplication::quit);
    return a.exec();
}

      QT += core
SOURCES += main.cpp
QMAKE_CXXFLAGS += -fstack-protector
win32: LIBS += -lssp
      1. In setCursor() the program crashes. If you remove stack protection by removing the last two lines in the .pro file, the error goes away.

      Attachments

        1. qtbug_89678.png
          9 kB
          Christian Ehrlicher

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-89675 Functions using QSettings crash with -fstack-protector on

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-89676 QTableWidgetItem::setText() crashes with -fstack-protector on

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              thiago Thiago Macieira
              szotsaki Szőts Ákos
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes