[Rpm-maint] Fwd: Re: How to proceed with MiniDebugInfo

[Phil Knirsch]

Hi guys.

As the minidebuginfo feature has now been approved by FESCO for Fedora 
18 Alex asked me to get the necessary patches for rpm properly reviewed 
and integrated into rpm.

So here's the email :)

Thanks guys!

Regards, Phil

-------- Original Message --------
Subject: Re: [Rpm-maint] How to proceed with MiniDebugInfo
Date: Mon, 11 Jun 2012 12:14:46 +0200
From: Alexander Larsson <alexl at redhat.com>
To: Development discussions related to Fedora 
<devel at lists.fedoraproject.org>,        rpm-maint at lists.rpm.org

On Fri, 2012-05-25 at 10:10 +0300, Panu Matilainen wrote:
> On 05/25/2012 09:26 AM, Alexander Larsson wrote:
> > On Thu, 2012-05-24 at 13:20 -0400, Casey Dahlin wrote:
> >> On Thu, May 24, 2012 at 09:28:16AM +0200, Alexander Larsson wrote:
> >>> I'm at a loss to how to proceed with the MiniDebugInfo work. I have
> >>> patches to rpmbuild that creates the compressed minidebuginfo putting
> >>> them in the main binaries, and I have patches to gdb that reads the
> >>> compressed debuginfo on demand.
> >>>
> >>> However, the whole thing is useless unless we agree that we want to
> >>> enable this by default. It seems some people like the idea, whereas
> >>> others disagree that its worth the increased binary size. It doesn't
> >>> look like either side is gonna be able to convince the other side, so
> >>> how do we get to a decision here?
> >>>
> >>
> >> Just go do it. See who actually shows up to stop you.
> >
> > To actually get the debuginfo in the builds all I need is a minor patch
> > to the find-debuginfo.sh script in rpm-build. However, since the effect
> > of it is global it seems to me that its a wider decision than just the
> > maintainer of rpm-build.
>
> As long as the behavior is optional and configurable, just send the
> patch to rpm-maint and we'll see. Fedora isn't the only consumer of rpm,
> and somebody else might find it useful regardless of whether Fedora
> wants to enable the thing or not.

Ok, here goes:

* rpm-minidebuginfo.patch
   Patches find-debuginfo.sh and adds new _include_minidebuginfo option
   defaulting to off
* redhat-rpm-config-minidebug.patch
   Example patch that enables building minidebuginfo by default on Fedora

* 0001-configure.ac-Look-for-and-use-libzma-on-ELF-systems.patch
* 0002-Support-lzma-compressed-.gnu_debugdata-sections.patch
   Gdb patches enabling on-demand lzma decompression of
   the .gnu_debugdata section looking for separate debuginfo there.

With these patches all applied any rpm you build (that doesn't
explicitly disable debuginfo generation) will get xz compresses minimal
debug info that gdb will find automatically (unless the real debuginfo
is installed, then that will be used).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpm-minidebuginfo.patch
Type: text/x-patch
Size: 3743 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20120619/512a4113/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: redhat-rpm-config-minidebug.patch
Type: text/x-patch
Size: 466 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20120619/512a4113/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-configure.ac-Look-for-and-use-libzma-on-ELF-systems.patch
Type: text/x-patch
Size: 2343 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20120619/512a4113/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Support-lzma-compressed-.gnu_debugdata-sections.patch
Type: text/x-patch
Size: 7888 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20120619/512a4113/attachment-0003.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Attached Message Part
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20120619/512a4113/attachment.ksh>