Created attachment 759209 [details] specfile patch that turns on MDI support and adds the other attachment as a patch ABRT would like to take advantage of the MiniDebugInfo[1] feature present in F19 through the libunwind library. The support for MiniDebugInfo is not built in though and furthermore the MiniDebugInfo implementation in libunwind-1.1 contains a bug which prevents the correct operation anyway. To turn on the MiniDebugInfo support, it is sufficient to add xz-devel to BuildRequires and the specfile patch does that. The second patch is against libunwind-1.1 and fixes the above mentioned bug. It has been sent to the upstream mailing list[2] with no reply so far. The specfile patch adds it to the patch series. Do you think it would be possible to include the MiniDebugInfo support in the next F19 release of the libunwind package? [1] http://fedoraproject.org/wiki/Features/MiniDebugInfo [2] http://lists.nongnu.org/archive/html/libunwind-devel/2013-06/msg00000.html
Created attachment 759210 [details] patch for libunwind-1.1 minidebuginfo bug preventing the correct operation
Created attachment 759278 [details] specfile patch that turns on MDI support and adds the other attachment as a patch New spec patch: - against *current* specfile - increments release - adds changelog entry
If you decide to fix this issue, could you please push the build to F18 as well?
(In reply to Martin Milata from comment #2) > Created attachment 759278 [details] > specfile patch that turns on MDI support and adds the other attachment as a > patch > > New spec patch: > - against *current* specfile > - increments release > - adds changelog entry Requires: xz is needed, isn't it?
If you enables minidebuginfo feature, could you also introduce the patch submitted in [1]? [1] http://lists.nongnu.org/archive/html/libunwind-devel/2013-07/msg00001.html [Libunwind-devel] [PATCH] Missing -llzma in libunwind.pc liblzuma used in decoding MiniDebuginfo is not listed in libunwind.pc.
If you enable minidebuginfo feature, could you also introduce the patch submitted in [1]? [1] http://lists.nongnu.org/archive/html/libunwind-devel/2013-07/msg00001.html [Libunwind-devel] [PATCH] Missing -llzma in libunwind.pc liblzuma used in decoding MiniDebuginfo is not listed in libunwind.pc.
The patch is merged. http://git.savannah.gnu.org/cgit/libunwind.git/commit/?h=v0.98-stable&id=dee708f4bc9aa169bd96e97c5e5ac851a10c7868.
The bugfix (attachment 759210 [details]) has been merged upstream: http://git.savannah.gnu.org/cgit/libunwind.git/commit/?id=65ac86741606e1d87aef75755c699e4fa6884230
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.