Bug #33252 Add the mysqld.debug to tarball packages

Description:
The RPM debuginfo package has a mysqld.debug which can be used with a core file generated from the default mysqld to debug the core file further.

According to Danny, this file is debug information stripped from the binary after being compiled with -g.

This file is different than mysqld-debug which is a server compiled with full debug (and is much slower in many cases due to the extra debug information).

How to repeat:
Try to debug a core file.  With the RPM you can use mysqld.debug to get a lot more information (such as line numbers, arguments passed, etc...) which is normally only available from a mysqld-debug core debug.

Suggested fix:
Create a mysqld.debug for tarball packages too.

I have added -g to our internal build scripts so that the generated mysqld (and other binaries) will have debug symbols added.  This will be present in 5.0.60, 5.1.24-rc and 6.0.5-alpha.

Note that for tarball packages the default 'mysqld' will have symbols available, we do not need to generate a separate mysqld.debug as we do for RPM which strips binaries by default.

Noted in 5.0.60, 5.1.24, 6.0.5 changelogs.

For binary .tar.gz packages, mysqld and other binaries now are
compiled with debugging symbols included to enable easier use with a
debugger.

It doesn't look like it is working.  I do not see debugging information in 5.0.60 Linux AMD64 binaries (mysql-enterprise-gpl-5.0.60-linux-x86_64-glibc23).

It doesn't look like it is working.  I do not see debugging information in 5.0.60 Linux AMD64 binaries (mysql-enterprise-gpl-5.0.60-linux-x86_64-glibc23).

Harrison,

I think we covered all the packages now, do you still see any without the debug information?

Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".