Bug 781736 - Process /var/lib/boinc/projects/setiathome.berkeley.edu/astropulse_5.06_x86_64-pc-linux-gnu was killed by signal 11 (SIGSEGV)
Summary: Process /var/lib/boinc/projects/setiathome.berkeley.edu/astropulse_5.06_x86_6...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Milos Jakubicek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-14 18:19 UTC by Robert Kief
Modified: 2012-06-26 12:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-26 12:59:47 UTC
Type: ---


Attachments (Terms of Use)

Description Robert Kief 2012-01-14 18:19:28 UTC
Description of problem:The bug reporting icon appeared after restarting my computer yesterday.  The tool reported seven apparently identical bugs dated 01/11/2012 - 01/13/2012.  No additional bugs have appeared since the seventh bug.  I was unable to report these bugs using the Reporting Tool because a backtrace wasn't generated.


Version-Release number of selected component (if applicable): 6.12.35


How reproducible: Unknown


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: This is a copy of the log showing the backtrace failure:

--- Running analyze_LocalGDB ---
Analyzing coredump 'coredump'
Coredump references 1 debuginfo files, 1 of them are not installed
Setting up yum repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
Missing debuginfo file: /usr/lib/debug/.build-id/ee/01073456c86c3a349e64d2e4090d57b17f0a2c.debug
Generating backtrace
Can't set gid 989: Operation not permitted
Backtrace is generated and saved, 0 bytes
Can't open file './component': No such file or directory
Backtrace parsing failed for .
1:0: No frame and no thread found.

Comment 1 Robert Kief 2012-01-14 18:27:22 UTC
Seti@home appears to be running normally at this time.

Comment 2 Milos Jakubicek 2012-06-26 12:59:47 UTC
It looks like this was a bug in that particular project application, not boinc itself, I'm closing for now.


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