Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-658

LP:842688 - Ubuntu and packages don't contain debug info

Details

    Description

      I unpacked all .deb files that were built for karmic_amd64 platform (just picked one at random), and for mysqld binary the archives have:

      ./usr/sbin/mysqld: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.6.15, stripped

      and no debuginfo file. It is bad that we are not shipping debug information - if we're reported crashes we won't be able to fully analyze them.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-572 No debug symbols for Ubuntu packages

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Technical task - A technical task. MDBF-727 Use Docker instead of KVM

          • Major - Major loss of function.
          • Closed

          Technical task - A technical task. MDBF-739 Compile special release binaries with symbols

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-4646 No mysqld-debug or debuginfo in MariaDB-Server RPM

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 20 older comments
            dbart Daniel Bartholomew added a comment -

            danblack: I took a look at the differences between the dh_strip in stretch (version 0.031-1) and the version currently in jessie-backports (version 0.031-1~bpo8+1) and yes, there is one difference:

            --- dh_strip-stretch	2017-03-17 12:27:10.339611257 -0400
            		 
            +++ dh_strip-jessie-0.031-1~bpo8+1	2017-03-17 12:57:01.018522537 -0400
            		 
            @@ -166,6 +166,10 @@
            		 
             	error("--dbgsym-migration and --no-automatic-dbgsym are mutually exclusive");
            		 
             }
            		 
             
            +# UNCONDITIONALLY disable this as we need a new version of dpkg-dev
            		 
            +# for this to work
            		 
            +$dh{ENABLE_DBGSYM} = 0;
            		 
            +
            		 
             # This variable can be used to turn off stripping (see Policy).
            		 
             if (get_buildoption('nostrip')) {
            		 
             	exit;

            dbart Daniel Bartholomew added a comment - danblack : I took a look at the differences between the dh_strip in stretch (version 0.031-1) and the version currently in jessie-backports (version 0.031-1~bpo8+1) and yes, there is one difference: --- dh_strip-stretch 2017-03-17 12:27:10.339611257 -0400 +++ dh_strip-jessie-0.031-1~bpo8+1 2017-03-17 12:57:01.018522537 -0400 @@ -166,6 +166,10 @@ error("--dbgsym-migration and --no-automatic-dbgsym are mutually exclusive"); } +# UNCONDITIONALLY disable this as we need a new version of dpkg-dev +# for this to work +$dh{ENABLE_DBGSYM} = 0; + # This variable can be used to turn off stripping (see Policy). if (get_buildoption('nostrip')) { exit;
            danblack Daniel Black added a comment -

            dbart, yes that would be the difference I mentioned in (3.) here https://jira.mariadb.org/browse/MDEV-658?focusedCommentId=92965&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-92965 . I couldn't see how the dpkg-dev versioning had an effect on this.

            So have you all the information needed for debug packages on Debian and Ubuntu?

            Although you observed compat 9 wasn't required for operation did you see added compression of the debug package as a result of it (https://www.mankier.com/7/debhelper#Compatibility_Levels)? Where filenames in the debug packages different?

            danblack Daniel Black added a comment - dbart , yes that would be the difference I mentioned in (3.) here https://jira.mariadb.org/browse/MDEV-658?focusedCommentId=92965&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-92965 . I couldn't see how the dpkg-dev versioning had an effect on this. So have you all the information needed for debug packages on Debian and Ubuntu? Although you observed compat 9 wasn't required for operation did you see added compression of the debug package as a result of it ( https://www.mankier.com/7/debhelper#Compatibility_Levels)? Where filenames in the debug packages different?
            danblack Daniel Black added a comment - - edited

            So 5.5 has no debug syms.
            (Debian):
            10.0 has a 10.0.30 debug package for x86_64/i386 but not for ppc64le or 10.0.31
            10.1 has 10.1.22 and 10.1.23 (x86_64 only) but not 10.1.24
            10.2 has recent debug symbols packages for recent releases of x86_64/i386 but not ppc64le.

            danblack Daniel Black added a comment - - edited So 5.5 has no debug syms. (Debian): 10.0 has a 10.0.30 debug package for x86_64/i386 but not for ppc64le or 10.0.31 10.1 has 10.1.22 and 10.1.23 (x86_64 only) but not 10.1.24 10.2 has recent debug symbols packages for recent releases of x86_64/i386 but not ppc64le.
            otto Otto Kekäläinen added a comment -

            FYI: https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#debug-archive

            otto Otto Kekäläinen added a comment - FYI: https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#debug-archive
            danblack Daniel Black added a comment -

            Thanks otto, will use that in the next updated of the KB related to debugging.

            danblack Daniel Black added a comment - Thanks otto , will use that in the next updated of the KB related to debugging.

            People

              dbart Daniel Bartholomew
              psergei Sergei Petrunia
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.