Bug 1477022 - dwz segfaults on xscreensaver rebuild
Summary: dwz segfaults on xscreensaver rebuild
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dwz
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 05:40 UTC by Mamoru TASAKA
Modified: 2018-11-30 17:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 17:39:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mamoru TASAKA 2017-08-01 05:40:06 UTC
Description of problem:

Just rebuilding xscreensaver on rawhide causes dwz segfault.


Version-Release number of selected component (if applicable):
xscreensaver-5.37-2.fc27.1
dwz-0.12-3.fc26

How reproducible:
Seems 100%

Steps to Reproduce:
1. fedpkg co --branches xscreensaver
2. cd xscreensaver/master
3. fedpkg build --scratch

Actual results:
https://kojipkgs.fedoraproject.org//packages/xscreensaver/5.37/2.fc27.1/data/logs/x86_64/
see build.log

extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/energystream
extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/fluidballs
extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/queens
extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/boxed
extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/halftone
extracting debug info from /builddir/build/BUILDROOT/xscreensaver-5.37-2.fc27.1.x86_64/usr/libexec/xscreensaver/slip
/usr/lib/rpm/find-debuginfo.sh: line 518: 44847 Segmentation fault      (core dumped) dwz $dwz_opts ${dwz_files[@]}
/usr/lib/rpm/sepdebugcrcfix: Updated 227 CRC32s, 0 CRC32s did match.
36933 blocks

Expected results:
Does not segfault

Additional info:

Comment 1 Jan Kurik 2017-08-15 07:00:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 2 Ben Cotton 2018-11-27 18:38:16 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

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

Comment 3 Ben Cotton 2018-11-30 17:39:09 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.


Note You need to log in before you can comment on or make changes to this bug.