Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Segmentation fault in drawComplexControl() with Gtk style (Qt 4.8.1)
Forum Updated to NodeBB v4.3 + New Features

Segmentation fault in drawComplexControl() with Gtk style (Qt 4.8.1)

Scheduled Pinned Locked Moved General and Desktop
3 Posts 2 Posters 2.6k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    toralf
    wrote on last edited by
    #1

    After upgrading to Qt 4.8.1, the application I'm working on got very unstable if the Gtk style (which is my default) is used - I get frequent segfaults for simple operations. The first few call stack entries when this occurs are:

    #0 0x00000000 in ?? ()
    #1 0x00e7d178 in QGtkStyle::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const ()
    from /usr/lib/qt4/lib/libQtGui.so.4
    #2 0x00f82ae5 in QScrollBar::paintEvent(QPaintEvent*) ()
    from /usr/lib/qt4/lib/libQtGui.so.4
    #3 0x00ad1494 in QWidget::event(QEvent*) () from /usr/lib/qt4/lib/libQtGui.so.4
    #4 0x00ece894 in QAbstractSlider::event(QEvent*) ()

    It turns out that I can also reproduce this problem with (at least) one of the example applications - the "tabdialog". Steps to reproduce become:

    Make sure "GTK+" is selected as GUI Style in Qt Configuration, or alternatively, "Desktop Settings" on a GNOME based system.

    /usr/lib/qt4/examples/dialogs/tabdialog/tabdialog (but substitute your Qt root for /usr/lib/qt4 as appropriate.)

    Select the "Applications" tab.

    This result in the good (or bad) old
    Segmentation fault (core dumped)

    That's on a system running CentOS 5.8, 32-bit.

    Does anyone else have this problem?

    1 Reply Last reply
    0
    • A Offline
      A Offline
      alleym1
      wrote on last edited by
      #2

      My Debian 5.0 build also produces this exact core file whenever I attempt to launch a Qt binary (designer, linguist, assistant).

      1 Reply Last reply
      0
      • T Offline
        T Offline
        toralf
        wrote on last edited by
        #3

        Right. Thanks.

        I've now filed a bug report for this: https://bugreports.qt-project.org/browse/QTBUG-25760

        I've looked at the Qt source code, too, and I think I know how the problem could be fixed. I'll add more details to the QtBug...

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved