Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. QT 5.15.0 install :
Forum Updated to NodeBB v4.3 + New Features

QT 5.15.0 install :

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
77 Posts 5 Posters 19.5k Views 2 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.
  • hskoglundH hskoglund

    Yeah, it's trying to start Python I think.

    One idea you haven't tried (I think): go to Settings and create a new user, logout and login as the new user. Then try gdb.exe when logged in as that new user.

    D Offline
    D Offline
    dahu74fr
    wrote on last edited by
    #62

    @hskoglund OK. I try.

    1 Reply Last reply
    0
    • hskoglundH hskoglund

      Yeah, it's trying to start Python I think.

      One idea you haven't tried (I think): go to Settings and create a new user, logout and login as the new user. Then try gdb.exe when logged in as that new user.

      D Offline
      D Offline
      dahu74fr
      wrote on last edited by
      #63

      @hskoglund I tried with a new account and i have the same thing.

      1 Reply Last reply
      0
      • hskoglundH Offline
        hskoglundH Offline
        hskoglund
        wrote on last edited by
        #64

        About why python does not work good for gdb, could you check the python installation in Qt:

        cd C:\Programmation\Qt\Tools\mingw810_64\opt\bin
        python -c "print 2+2"
        

        If the python command works and prints "4" then could you try the same with the verbose flag:

        python -v -c "print 2+2"
        

        and post the output here...

        D 1 Reply Last reply
        1
        • hskoglundH hskoglund

          About why python does not work good for gdb, could you check the python installation in Qt:

          cd C:\Programmation\Qt\Tools\mingw810_64\opt\bin
          python -c "print 2+2"
          

          If the python command works and prints "4" then could you try the same with the verbose flag:

          python -v -c "print 2+2"
          

          and post the output here...

          D Offline
          D Offline
          dahu74fr
          wrote on last edited by
          #65

          @hskoglund Yes it seams to work :
          4820164e-62d1-4e8d-ac4b-f6d0e16b3631-image.png
          and :
          669cb975-c9a6-406f-89b3-67a4d16c7a77-image.png 5d3d1e3b-f7e8-4230-8bd3-616aaae15ec0-image.png a5a6e75a-9e52-43e8-8713-99ef94b1a609-image.png

          1 Reply Last reply
          0
          • hskoglundH Offline
            hskoglundH Offline
            hskoglund
            wrote on last edited by
            #66

            Ok, looks good. I think to see why your gdb.exe does not run, we need to trace it using Process Monitor, download it here

            Here's what you do:
            start Process Monitor (procmon.exe), type ctrl+L to show the Filter dialog box, in that dialog in the top left corner, in the drop-down list, select "Process Name", then check that the next drop-down list selects "Is" then in the edit box type gdborig.exe and the click the Add button. After that it should look like this:
            Screenshot 2020-07-15 at 11.46.05.png Click OK button to close the dialog box.

            Then start gdb.exe as we did before:

            C:\Programmation\Qt\Tools\mingw810_64\bin\gdb.exe
            

            Now entries should be seen in ProcMon, like this:
            Screenshot 2020-07-15 at 11.47.03.png
            My ProcMon shows 2315 entries for gdborig.exe but your output should be shorter (since it fails) post here say the last 50 lines before it stops.

            Note: you can clear the display of ProcMon using ctrl+X

            D 1 Reply Last reply
            1
            • hskoglundH hskoglund

              Ok, looks good. I think to see why your gdb.exe does not run, we need to trace it using Process Monitor, download it here

              Here's what you do:
              start Process Monitor (procmon.exe), type ctrl+L to show the Filter dialog box, in that dialog in the top left corner, in the drop-down list, select "Process Name", then check that the next drop-down list selects "Is" then in the edit box type gdborig.exe and the click the Add button. After that it should look like this:
              Screenshot 2020-07-15 at 11.46.05.png Click OK button to close the dialog box.

              Then start gdb.exe as we did before:

              C:\Programmation\Qt\Tools\mingw810_64\bin\gdb.exe
              

              Now entries should be seen in ProcMon, like this:
              Screenshot 2020-07-15 at 11.47.03.png
              My ProcMon shows 2315 entries for gdborig.exe but your output should be shorter (since it fails) post here say the last 50 lines before it stops.

              Note: you can clear the display of ProcMon using ctrl+X

              D Offline
              D Offline
              dahu74fr
              wrote on last edited by
              #67

              @hskoglund
              I think you have 2315 entries when you look at the bottom of the window. For me i have 362 entries only.
              a301ea80-7037-4360-a64c-afc916a4bb3d-image.png
              I tried an other time and now 356 entries.
              bcb8610e-0d98-40d8-9eac-c6f9c7eecaf7-image.png

              1 Reply Last reply
              0
              • hskoglundH Offline
                hskoglundH Offline
                hskoglund
                wrote on last edited by
                #68

                Ok, could you scroll down in the ProcMon window, so the last lines (before it stops) of the output is shown?

                D 1 Reply Last reply
                0
                • hskoglundH hskoglund

                  Ok, could you scroll down in the ProcMon window, so the last lines (before it stops) of the output is shown?

                  D Offline
                  D Offline
                  dahu74fr
                  wrote on last edited by
                  #69

                  @hskoglund Here are the latest lines :
                  05d7c75b-d600-4ec3-8edd-2061ae7e0db7-image.png
                  And with scroll on the right :
                  47c8050d-f897-4d5c-82d3-e97cda8c28a2-image.png

                  1 Reply Last reply
                  0
                  • hskoglundH Offline
                    hskoglundH Offline
                    hskoglund
                    wrote on last edited by hskoglund
                    #70

                    Thanks, now I can see the gdborig.exe crash in the Procmon output (the C:\Windows\System32\WerFault.exe line)
                    To see the crash info, click on the Start button and type event then select Event Viewer
                    In the left column, select Windows Logs and then click on Application, then in the middle window, in the Source column, do you see any gdborig lines? If yes, click on them to see more info in the lower (General) window.

                    Edit: gdborig.exe seems to crash when trying to read the C:\msys64\etc\termcap file. If you have MSYS2 installed, try removing or renaming that file.
                    Or you could try removing MSYS2 completely (click on Start button, type add or , select Add or Remove programs then search for MSYS2 64-bit in the list, click on it and select Uninstall).

                    D 1 Reply Last reply
                    2
                    • hskoglundH hskoglund

                      Thanks, now I can see the gdborig.exe crash in the Procmon output (the C:\Windows\System32\WerFault.exe line)
                      To see the crash info, click on the Start button and type event then select Event Viewer
                      In the left column, select Windows Logs and then click on Application, then in the middle window, in the Source column, do you see any gdborig lines? If yes, click on them to see more info in the lower (General) window.

                      Edit: gdborig.exe seems to crash when trying to read the C:\msys64\etc\termcap file. If you have MSYS2 installed, try removing or renaming that file.
                      Or you could try removing MSYS2 completely (click on Start button, type add or , select Add or Remove programs then search for MSYS2 64-bit in the list, click on it and select Uninstall).

                      D Offline
                      D Offline
                      dahu74fr
                      wrote on last edited by
                      #71

                      @hskoglund
                      Here is the report in event :
                      9c1d11c6-dd1b-4bef-9bb1-467f28b5a3c1-image.png
                      I looked for msys2, but i have not installed this thing. And i can't found it in installed applications.

                      1 Reply Last reply
                      0
                      • hskoglundH Offline
                        hskoglundH Offline
                        hskoglund
                        wrote on last edited by
                        #72

                        Could you try to start gdb.exe this way:

                        C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --nx
                        

                        (the --nx means: do nor read any .gdbinit files)

                        D 1 Reply Last reply
                        1
                        • hskoglundH hskoglund

                          Could you try to start gdb.exe this way:

                          C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --nx
                          

                          (the --nx means: do nor read any .gdbinit files)

                          D Offline
                          D Offline
                          dahu74fr
                          wrote on last edited by
                          #73

                          @hskoglund said in QT 5.15.0 install ::

                          C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --nx

                          Nothing more :
                          3e7017ab-0e74-41b0-803a-410c097444ce-image.png

                          1 Reply Last reply
                          0
                          • hskoglundH Offline
                            hskoglundH Offline
                            hskoglund
                            wrote on last edited by
                            #74

                            Could you also try:

                            C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --configuration
                            
                            D 1 Reply Last reply
                            0
                            • hskoglundH hskoglund

                              Could you also try:

                              C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --configuration
                              
                              D Offline
                              D Offline
                              dahu74fr
                              wrote on last edited by
                              #75

                              @hskoglund said in QT 5.15.0 install ::

                              C:\Programmation\Qt\Tools\mingw810_64\bin\gdb --configuration

                              Nothing :
                              df6536f0-e2eb-42fc-a243-8e18f5a128bc-image.png

                              1 Reply Last reply
                              0
                              • hskoglundH Offline
                                hskoglundH Offline
                                hskoglund
                                wrote on last edited by
                                #76

                                Huh, no good luck today :-(

                                Ok we know that gdborig.exe crashes in msvcrt.dll with Access Violation 0xc0000005 but googling that usually only says "try upgrading your Windows 10 or try upgrading your version of MinGW"

                                But you already have the latest of both. Maybe you have to wait for Qt 5.15.1...

                                D 1 Reply Last reply
                                3
                                • hskoglundH hskoglund

                                  Huh, no good luck today :-(

                                  Ok we know that gdborig.exe crashes in msvcrt.dll with Access Violation 0xc0000005 but googling that usually only says "try upgrading your Windows 10 or try upgrading your version of MinGW"

                                  But you already have the latest of both. Maybe you have to wait for Qt 5.15.1...

                                  D Offline
                                  D Offline
                                  dahu74fr
                                  wrote on last edited by
                                  #77

                                  @hskoglund OK.
                                  I will wait that my computer will be OK to have the latest Windows 10 version. I have the 1909 and the latest is 2004.
                                  And i will wait for a new version of Qt.
                                  Or i will reinstall Windows and all my softwares, but it takes a long time.
                                  And thank you very much for your help.
                                  Best regards.

                                  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