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. Qt software debugging techniques
Forum Updated to NodeBB v4.3 + New Features

Qt software debugging techniques

Scheduled Pinned Locked Moved Solved General and Desktop
8 Posts 2 Posters 755 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.
  • C Offline
    C Offline
    Cobra91151
    wrote on 21 Feb 2019, 19:47 last edited by Cobra91151
    #1

    Hi! I have the application which is published to the Microsoft Store, under health page for the application in the Dev center, it reports crash issue:

    fail_fast_fatal_app_exit_c0000409_qt5core.dll!qt_logging_to_console

    And stack trace:

    0	ucrtbase.dll	abort	0x000000000000004E
    1	Qt5Core.dll	qt_logging_to_console	0x000000000000017A
    2	Qt5Core.dll	QMessageLogger::fatal	0x0000000000000093
    3	Qt5Gui.dll	QPixmap::paintEngine	0x0000000000000052
    4	Qt5Gui.dll	QPixmap::QPixmap	0x0000000000000037
    

    When debugging the application I don't get any crashes. The question is how to get the crash location or function line/name in the code by the stack trace? Any ideas? Thanks.

    1 Reply Last reply
    0
    • S Offline
      S Offline
      SGaist
      Lifetime Qt Champion
      wrote on 21 Feb 2019, 19:58 last edited by
      #2

      Hi,

      If you have a crash in release mode and not in debug, check that you properly initialise all your pointer variables.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      C 1 Reply Last reply 21 Feb 2019, 20:09
      2
      • S SGaist
        21 Feb 2019, 19:58

        Hi,

        If you have a crash in release mode and not in debug, check that you properly initialise all your pointer variables.

        C Offline
        C Offline
        Cobra91151
        wrote on 21 Feb 2019, 20:09 last edited by
        #3

        @SGaist

        Thanks, but the project is big and checking all pointer variables is not an option. I need at least name of source file or class to check for it.

        1 Reply Last reply
        0
        • S Offline
          S Offline
          SGaist
          Lifetime Qt Champion
          wrote on 21 Feb 2019, 21:20 last edited by
          #4

          Out of curiosity, how big is that ?

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          C 1 Reply Last reply 21 Feb 2019, 21:23
          0
          • S SGaist
            21 Feb 2019, 21:20

            Out of curiosity, how big is that ?

            C Offline
            C Offline
            Cobra91151
            wrote on 21 Feb 2019, 21:23 last edited by
            #5

            @SGaist

            It's about 286 files.

            1 Reply Last reply
            0
            • S Offline
              S Offline
              SGaist
              Lifetime Qt Champion
              wrote on 21 Feb 2019, 21:30 last edited by
              #6

              I feared it was a bigger number.

              From you stack trace, it's QPixmap related, so you should start by checking the parts which are using or creating QPixmap.

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              C 2 Replies Last reply 21 Feb 2019, 21:32
              4
              • S SGaist
                21 Feb 2019, 21:30

                I feared it was a bigger number.

                From you stack trace, it's QPixmap related, so you should start by checking the parts which are using or creating QPixmap.

                C Offline
                C Offline
                Cobra91151
                wrote on 21 Feb 2019, 21:32 last edited by
                #7

                @SGaist

                Ok. I will check it and reply later. Thanks.

                1 Reply Last reply
                0
                • S SGaist
                  21 Feb 2019, 21:30

                  I feared it was a bigger number.

                  From you stack trace, it's QPixmap related, so you should start by checking the parts which are using or creating QPixmap.

                  C Offline
                  C Offline
                  Cobra91151
                  wrote on 22 Feb 2019, 10:16 last edited by
                  #8

                  @SGaist

                  You was right. I think the problem was with programs icons creation/destruction on the fly and DestroyIcon destroyed the handle which was in use.

                  I added some improvements, now it only creates 1 object of HICON and QPixmap, then appends to the structure in the loop and after the loop exited it calls DestroyIcon function to destroy the HICON handle.

                  Also I have found this article about finding bugs from the Microsoft Store:
                  https://stackoverflow.com/questions/41527577/how-to-get-a-crash-dump-or-any-usable-crash-report-for-a-converted-windows-sto

                  But also I'm going to try StackWalker application to check for other issues. Thank you.

                  1 Reply Last reply
                  4

                  1/8

                  21 Feb 2019, 19:47

                  • Login

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