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. Crashing somewhere in Qt... how to... eee get src?
QtWS25 Last Chance

Crashing somewhere in Qt... how to... eee get src?

Scheduled Pinned Locked Moved Unsolved General and Desktop
qdebugdebug
6 Posts 3 Posters 779 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.
  • D Offline
    D Offline
    Dariusz
    wrote on 19 Jan 2022, 18:32 last edited by
    #1

    Hey

    Not quite sure how... but how can I get proper qt functions calls instead of this in my debug >
    46526f37-323c-4654-9cab-20fe05a24151-image.png
    Something somewhere died inside Qt :- )
    TIA!

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mchinand
      wrote on 19 Jan 2022, 18:47 last edited by
      #2

      If you installed Qt via the installer, you can use the MaintenanceTool to install the 'Qt Debug Information Files' for the version you are using. Note, you should also go back in the stack trace to see the last line of your code that was being executed before the crash occurred; it's more than likely that you have a bug in your code.

      D 1 Reply Last reply 19 Jan 2022, 19:02
      1
      • M mchinand
        19 Jan 2022, 18:47

        If you installed Qt via the installer, you can use the MaintenanceTool to install the 'Qt Debug Information Files' for the version you are using. Note, you should also go back in the stack trace to see the last line of your code that was being executed before the crash occurred; it's more than likely that you have a bug in your code.

        D Offline
        D Offline
        Dariusz
        wrote on 19 Jan 2022, 19:02 last edited by
        #3

        @mchinand Hey
        I agree, its definitely something I did. But there is no log at bottom that leads me to my issue. So I must have pushed it on thread and then banana happen.

        If I run QtCreator, how can I point to these files so I can see Qt source log/breakpoints? Do I need to download source too ?

        Regards
        Dariusz

        1 Reply Last reply
        0
        • D Offline
          D Offline
          Dariusz
          wrote on 9 Feb 2022, 09:17 last edited by Dariusz 2 Sept 2022, 09:19
          #4

          Yo

          Ok I'm having another stab at it... I'm on Clion atm & both QtCreator/clion fail to dive in to qt sources when debugging, duh. In any case, I had a bit more luck latelly.

          My Cmake copies QT dlls to my exe folder, but it did not copy pdb, now I copy pdb and I can see a little more data, yay! But no source... so I started to add src to my project, but not sure if that is the way, currently going with >

                  include_directories(${QT_PATH}src/qtbase)
                  include_directories(${QT_PATH}src/qtbase/src/)
                  include_directories(${QT_PATH}src/qtbase/src/widgets)
                  include_directories(${QT_PATH}src/qtbase/src/widgets/widgets)
                  include_directories(${QT_PATH}src/qtbase/src/gui)
                  include_directories(${QT_PATH}src/qtbase/src/gui/kernel)
                  include_directories(${QT_PATH}src/qtbase/src/corelib)
                  include_directories(${QT_PATH}src/qtbase/src/corelib/thread)
          

          I'm thinking of writing recursive folder include for my cmake project & point it at cmake src dir and let it loose. This is probably the wrong way of doing it ?
          Maybe >
          https://gist.github.com/Asher-/617872

          C 1 Reply Last reply 9 Feb 2022, 09:20
          0
          • D Dariusz
            9 Feb 2022, 09:17

            Yo

            Ok I'm having another stab at it... I'm on Clion atm & both QtCreator/clion fail to dive in to qt sources when debugging, duh. In any case, I had a bit more luck latelly.

            My Cmake copies QT dlls to my exe folder, but it did not copy pdb, now I copy pdb and I can see a little more data, yay! But no source... so I started to add src to my project, but not sure if that is the way, currently going with >

                    include_directories(${QT_PATH}src/qtbase)
                    include_directories(${QT_PATH}src/qtbase/src/)
                    include_directories(${QT_PATH}src/qtbase/src/widgets)
                    include_directories(${QT_PATH}src/qtbase/src/widgets/widgets)
                    include_directories(${QT_PATH}src/qtbase/src/gui)
                    include_directories(${QT_PATH}src/qtbase/src/gui/kernel)
                    include_directories(${QT_PATH}src/qtbase/src/corelib)
                    include_directories(${QT_PATH}src/qtbase/src/corelib/thread)
            

            I'm thinking of writing recursive folder include for my cmake project & point it at cmake src dir and let it loose. This is probably the wrong way of doing it ?
            Maybe >
            https://gist.github.com/Asher-/617872

            C Online
            C Online
            Christian Ehrlicher
            Lifetime Qt Champion
            wrote on 9 Feb 2022, 09:20 last edited by Christian Ehrlicher 2 Sept 2022, 09:21
            #5

            Why should including directories (which are even included already indirectly by linking against the appropriate Qt libs) should help anything during debugging? Strange idea...
            The debugger needs to know where the sources are - how you tell them is debugger specific and can maybe done via the IDE but I don't know CLion.

            Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
            Visit the Qt Academy at https://academy.qt.io/catalog

            D 1 Reply Last reply 10 Feb 2022, 15:54
            1
            • C Christian Ehrlicher
              9 Feb 2022, 09:20

              Why should including directories (which are even included already indirectly by linking against the appropriate Qt libs) should help anything during debugging? Strange idea...
              The debugger needs to know where the sources are - how you tell them is debugger specific and can maybe done via the IDE but I don't know CLion.

              D Offline
              D Offline
              Dariusz
              wrote on 10 Feb 2022, 15:54 last edited by
              #6

              @Christian-Ehrlicher I've no idea :D But it did not work.
              When I pause debug, I get symbols/etc but it says that symbols are different from source file... so I have to manually navigate to cpp file in qt/src/bla/bla/bla dir

              Feels like msvc DLL shipped with Qt does not match src that I can install... maybe I should build my own qt so that everything is definitely running one ver... odd.

              Still digging.

              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