Bug 692706

Summary: boinc client crashes at startup - fortify flags a buffer overflow in sprintf
Product: [Fedora] Fedora Reporter: Valdis Kletnieks <valdis.kletnieks>
Component: boinc-clientAssignee: Milos Jakubicek <xjakub>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cheekyboinc, mmahut, xjakub
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-19 20:41:01 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:
Attachments:
Description Flags
Tracebacks from crashing boinc none

Description Valdis Kletnieks 2011-03-31 21:29:37 UTC
Created attachment 489241 [details]
Tracebacks from crashing boinc

Description of problem:
boinc client crashes at startup.


Version-Release number of selected component (if applicable):
boinc-client-6.10.58-3.r22930svn.fc15.x86_64

How reproducible:
Happens every time, I issue the 'boinc' command and kersplat.

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


Expected results:


Additional info:

Comment 1 Milos Jakubicek 2011-04-01 05:38:23 UTC
Did you follow https://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc?

Comment 2 Valdis Kletnieks 2011-04-01 06:59:52 UTC
OK.. That didn't crash right off the bat, running it as a service.  I made the mistake of reading this page:

http://boinc.berkeley.edu/download.php

which pointed me to this one:

http://boinc.berkeley.edu/wiki/GPU_computing

which says:

"Get the latest driver

Run BOINC, and look at the Messages. If BOINC reports a GPU, your current driver is OK. Otherwise..."

which certainly made it sound like just running 'boinc' would produce the messages in question...

All the same, if the program wants to be run as a service and it's launched from a terminal, it should print a message *saying* so, and then exiting cleanly.  Having Fortify gun the binary down in the middle of a printf() is just busted. :)