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

Provide sufficient debug symbols with the pre-built binaries for Qt

    XMLWordPrintable

Details

    Description

      Debug symbols are necessary for debugging and profiling.

      On windows we need the .pdb files and on linux debug symbols can be delivered in separate files, too. The configure options for producing those (at least on linux) are "-force-debug-info -separate-debug-info". The resulting debug symbols could than be delivered as separate packages so that people who don't need them don't have to install them.

      On Windows PDBs can be generated by adding these flags for VS configuration:

      1. -Zi flag for compiler. It tells C compiler to create a "program database" debug information.

      2. /DEBUG /OPT:REF flags for linker. /DEBUG turns on the creation of PDB and /OPT:REF tells the linker to eliminate unreferenced data (this debug info) from a DLL.

      We need to check if our configure options already do this. If not, they should be fixed.

      Attachments

        Issue Links

          is duplicated by

          Suggestion - Public suggestions QTBUG-29668 Creation of *.pdb files for release binaries in a separate package...

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          is required for

          Technical task - A technical task. QTBUG-75048 Daily releasing work 1H2019

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed

          Technical task - A technical task. QTBUG-78080 Daily releasing work 2H2019

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-32582 Debug symbols missing for Qt 5.1.0 SDK under Linux

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-47402 Invalid signature for .pdb files in binary Windows package

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Task - A task that needs to be done. QTQAINFRA-1688 Coin/CI should support '-separate-debug-info'

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Suggestion - Public suggestions QTBUG-28915 pdb files should be distributed for visual studio debug build

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Suggestion - Public suggestions QTBUG-4232 Add pdb files to the Active Qt distribution

          • P4: Low - Would be nice to fix, but it's not very important.
          • Closed
          replaces

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-3739 The binary packages for Windows do not include the pdb files for the plugins

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Suggestion - Public suggestions QTBUG-10127 Provide debugging symbols for releases

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed

          Suggestion - Public suggestions QTBUG-45407 Qt for Windows should be shipped with PDBs for release binaries as well, not only debug

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-65818 Qt library files are huge

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              aksalova Akseli Salovaara
              cattell Matthew Cattell (Inactive)
              Votes:
              61 Vote for this issue
              Watchers:
              55 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: