Bug 954867

Summary: [faf] ccache-3.1.8-1.fc18.i686 SIGSEGV in read_manifest
Product: [Fedora] Fedora Reporter: abrt-bot <abrt-bot>
Component: ccacheAssignee: Ville Skyttä <ville.skytta>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: joel, ville.skytta
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: abrt_hash:9c8976786bf5f8dde5405178a47c5608ff44bf89 reports:26
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:55:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description abrt-bot 2013-04-22 12:53:06 UTC
Description of problem: 
Faf server recevied number of crash reports for this package.

Problem URL:
https://retrace.fedoraproject.org/faf/problems/bthash/9c8976786bf5f8dde5405178a47c5608ff44bf89

Version-Release number of selected component:
ccache-3.1.8-1.fc18.i686

Additional info:
first occurence: 2013-02-01 10:28 UTC
reports count: 26
executable: /usr/bin/ccache

Truncated backtrace:
#  Function               Path             Source                                      
0  read_manifest          /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/manifest.c:217  
1  manifest_get           /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/manifest.c:546  
2  calculate_object_hash  /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/ccache.c:1040   
3  ccache                 /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/ccache.c:2009   
4  ccache_main            /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/ccache.c:2282   
5  main                   /usr/bin/ccache  /usr/src/debug/ccache-3.1.9/main.c:28       


This ticket was created automatically. If this report is malformed or not helpful
please let us know on crash-catcher.org so we can improve it.

Comment 1 Ville Skyttä 2013-05-08 20:07:57 UTC
Seems that despite the filenames in the "Source" column, the rest of the report is against 3.1.8, at least the line numbers make more sense for it than 3.1.9. Would probably need more reproducer info to dig deeper into this...?

Comment 2 Joel Rosdahl 2013-05-09 13:02:18 UTC
> Would probably need more reproducer info to dig deeper into this...?

Yes, I think so as well.

Comment 3 Fedora End Of Life 2013-12-21 13:06:02 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 20:55:30 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.