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. Linux / Window default close button / Segmentation fault
Forum Update on Monday, May 27th 2025

Linux / Window default close button / Segmentation fault

Scheduled Pinned Locked Moved General and Desktop
4 Posts 3 Posters 1.7k Views
  • 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.
  • M Offline
    M Offline
    michaelPT
    wrote on last edited by
    #1

    Hi everybody,

    Linux machine:
    Ubuntu 12.04/Ubuntu Unity
    gcc-Version 4.6.3
    Qt5.0.2

    Starting an application from the console I'm currently facing a challenge regarding the windows default close button (Qt::WindowCloseButtonHint).

    100 events clicking on the close button I'm facing about 62% segmentation faults.

    After reimplementing "closeEvent(QCloseEvent *event)":
    event->ignore();
    emit globalQuit(); (A Signal that a QPushButton triggers too to "quit()" the QApplication) I'm still facing 28% segmentation faults in contrast to using the Quit-QPushButton itself which never causes a segmentation fault.

    This just happens on Linux and is not reproducible on a Mac e.g.

    Is there anybody having an idea about the reason?

    Thanks
    Michael

    1 Reply Last reply
    0
    • raven-worxR Offline
      raven-worxR Offline
      raven-worx
      Moderators
      wrote on last edited by
      #2

      [quote author="michaelPT" date="1369319154"]Is there anybody having an idea about the reason?[/quote]

      maybe...if you post the stack trace. ;)

      --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
      If you have a question please use the forum so others can benefit from the solution in the future

      1 Reply Last reply
      0
      • M Offline
        M Offline
        michaelPT
        wrote on last edited by
        #3

        I hope a "catchsegv" output helps.

        *** Segmentation fault
        Register dump:

        EAX: b2003d40 EBX: b2c43ff4 ECX: 00000000 EDX: 00000001
        ESI: 09ab8b98 EDI: 09ab8ba0 EBP: b2003d40 ESP: b29dc200

        EIP: b2bb69d3 EFLAGS: 00010282

        CS: 0073 DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b

        Trap: 0000000e Error: 00000014 OldMask: 00000000
        ESP/signal: b29dc200 CR2: b2bb69d3

        FPUCW: ffff037f FPUSW: ffff0020 TAG: ffffffff
        IPOFF: 00000000 CSSEL: 0000 DATAOFF: 00000000 DATASEL: 0000

        ST(0) 0000 0000000000000000 ST(1) 0000 0000000000000000
        ST(2) 0000 0000000000000000 ST(3) 0000 0000000000000000
        ST(4) 0000 0000000000000000 ST(5) 0000 0000000000000000
        ST(6) 0000 8000000000000000 ST(7) 0000 a000400000000000

        Backtrace:

        1 Reply Last reply
        0
        • T Offline
          T Offline
          tobias.hunger
          wrote on last edited by
          #4

          Nope, it does not. Run the application in the debugger and check the backtrace. It should point you into the right direction.

          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