MySQL Bugs: #33252: Add the mysqld.debug to tarball packages

Bug #33252	Add the mysqld.debug to tarball packages
Submitted:	14 Dec 2007 23:07	Modified:	23 May 16:19
Reporter:	Harrison Fisk
Status:	Open
Category:	Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0.52	OS:	Linux
Assigned to:	Jonathan Perkin	Target Version:	5.0+
Triage:	D4 (Minor) / R1 (None/Negligible) / E2 (Low)

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).