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

Qt should not SIGABRT on initialization failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P3: Somewhat important
    • None
    • 5.15.1
    • QPA
    • None
    • Linux/Wayland, Linux/X11, Linux/Other display system

    Description

      If all platform plugins failed to initialize, Qt calls qFatal which in turn calls abort. This causes SIGABRT and may generate a coredump.

      In the most common case it's because the connection to the display (Wayland, X11, whatever) is missing or failed, and a coredump will not help analyzing that at all.

      I suggest using _exit(1) instead, which has practically the same behaviour but avoids SIGABRT and therefore also a coredump.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            vestbo Tor Arne Vestbø
            vogtinator Fabian Vogt
            Veli-Pekka Heinonen Veli-Pekka Heinonen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes