Bug 1379869 - [abrt] rpm: rstrlenhash(): rpm killed by SIGSEGV
Summary: [abrt] rpm: rstrlenhash(): rpm killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f8c92d9603b676de10ee813681c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-28 00:04 UTC by Ahmed Noor Kader Mustajir B. Md Eusoff
Modified: 2017-08-08 17:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:39:22 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (7.86 KB, text/plain)
2016-09-28 00:04 UTC, Ahmed Noor Kader Mustajir B. Md Eusoff
no flags Details
File: cgroup (242 bytes, text/plain)
2016-09-28 00:04 UTC, Ahmed Noor Kader Mustajir B. Md Eusoff
no flags Details

Description Ahmed Noor Kader Mustajir B. Md Eusoff 2016-09-28 00:04:31 UTC
Version-Release number of selected component:
rpm-4.13.0-0.rc1.27.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        rpm -U glibc-2.23.1-10.fc24.x86_64.rpm glibc-all-langpacks-2.23.1-10.fc24.x86_64.rpm glibc-common-2.23.1-10.fc24.x86_64.rpm glibc-devel-2.23.1-10.fc24.x86_64.rpm glibc-headers-2.23.1-10.fc24.x86_64.rpm glibc-langpack-en-2.23.1-10.fc24.x86_64.rpm
crash_function: rstrlenhash
executable:     /usr/bin/rpm
global_pid:     4918
kernel:         4.7.2-201.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 rstrlenhash at rpmstrpool.c:96
 #1 rstrhash at rpmstrpool.c:97
 #2 depCacheKeyHash at ../lib/rpmhash.C:106
 #3 rpmdbProvides at depends.c:528
 #4 unsatisfiedDepend at depends.c:686
 #5 checkInstDeps at depends.c:760
 #6 rpmtsCheck at depends.c:1009
 #7 rpmcliTransaction at rpminstall.c:263
 #8 rpmInstall at rpminstall.c:612

Comment 1 Ahmed Noor Kader Mustajir B. Md Eusoff 2016-09-28 00:04:38 UTC
Created attachment 1205360 [details]
File: backtrace

Comment 2 Ahmed Noor Kader Mustajir B. Md Eusoff 2016-09-28 00:04:40 UTC
Created attachment 1205361 [details]
File: cgroup

Comment 3 Fedora End Of Life 2017-07-25 23:16:01 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 4 Fedora End Of Life 2017-08-08 17:39:22 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.