Bug 674046

Summary: [abrt] gpredict-1.2-2.fc14: __libc_message: Process /usr/bin/gpredict was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kirby <joekirby>
Component: gpredictAssignee: Marek Mahut <mmahut>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: eric, hamaa1vs, jkirby, mmahut
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1c57a215ce3b9837648aeda9fddf44004a78ea6f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-15 12:22:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Kirby 2011-01-31 13:09:03 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: gpredict
comment: After gpredict has been running for a while it crashes. Sometimes hours, sometimes days.
component: gpredict
crash_function: __libc_message
executable: /usr/bin/gpredict
kernel: 2.6.35.10-74.fc14.i686.PAE
package: gpredict-1.2-2.fc14
rating: 4
reason: Process /usr/bin/gpredict was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296477818
uid: 500

How to reproduce
-----
1. Simply running gpredict
2.
3.

Comment 1 Kirby 2011-01-31 13:09:07 UTC
Created attachment 476180 [details]
File: backtrace

Comment 2 hamaa1vs 2011-02-02 19:27:43 UTC
Do you have a limit on the sometime days?  I have installed FC14 in a virtual machine and am waiting.

Also this has been added to the upstream bug tracker. 
<http://sourceforge.net/tracker/?func=detail&aid=3169184&group_id=213550&atid=1026162>

Comment 3 Joe Kirby 2011-02-02 20:40:31 UTC
IIRC 3 days is about the max. I will use this entry as the marker for the next report. gpredict has been up for about 180 minutes.

Comment 4 hamaa1vs 2011-03-15 11:40:40 UTC
I have been unable to replicate this in my fedora virtual machine.

Comment 5 Joe Kirby 2011-03-15 12:22:07 UTC
After having a number of crashes, I have not had a single problem since I filed the bug.