Bug 692706 - boinc client crashes at startup - fortify flags a buffer overflow in sprintf
Summary: boinc client crashes at startup - fortify flags a buffer overflow in sprintf
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milos Jakubicek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 21:29 UTC by Valdis Kletnieks
Modified: 2011-08-19 20:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-19 20:41:01 UTC
Type: ---


Attachments (Terms of Use)
Tracebacks from crashing boinc (8.77 KB, text/plain)
2011-03-31 21:29 UTC, Valdis Kletnieks
no flags Details

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. :)


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