Bug 1116475

Summary: [abrt] kcachegrind: hotshot2calltree:347:run_with_optparse:IndexError: list index out of range
Product: [Fedora] Fedora Reporter: Jon Dufresne <jon.dufresne>
Component: kcachegrindAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jgrulich, kevin, ltinkl, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fffe53eb53816cfa89be3fa3e41da85cafc18102
Whiteboard: abrt_hash:6727ef8157ac8c905c03b0edf96e32acabc7b33e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:28:29 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
File: backtrace
none
File: environ none

Description Jon Dufresne 2014-07-04 23:16:23 UTC
Description of problem:
Every time I run hotshot2calltree.

Version-Release number of selected component:
kcachegrind-4.12.5-1.fc20

Additional info:
reporter:       libreport-2.2.2
cmdline:        python /usr/bin/hotshot2calltree --help
executable:     /usr/bin/hotshot2calltree
kernel:         3.14.9-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
hotshot2calltree:347:run_with_optparse:IndexError: list index out of range

Traceback (most recent call last):
  File "/usr/bin/hotshot2calltree", line 391, in <module>
    run()
  File "/usr/bin/hotshot2calltree", line 347, in run_with_optparse
    versiontext = "%s version: %s" % ( progname, version.split()[1], )
IndexError: list index out of range

Local variables in innermost frame:

Comment 1 Jon Dufresne 2014-07-04 23:16:27 UTC
Created attachment 914772 [details]
File: backtrace

Comment 2 Jon Dufresne 2014-07-04 23:16:28 UTC
Created attachment 914773 [details]
File: environ

Comment 3 Jon Dufresne 2014-07-04 23:18:23 UTC
Looking at the script, the version values is set as: version = "$Revision$" so the call to split will never split this into more than one element. It looks like the value was intended to be replaced with something useful.

Comment 4 Jon Dufresne 2014-07-05 18:33:33 UTC
I downloaded and compiled the upstream version found here:

<http://www.kde.org/info/4.13.2.php>
<http://download.kde.org/stable/4.13.2/src/kcachegrind-4.13.2.tar.xz>

And this has been fixed. Any way this fix could be integrated with version shipped by Fedora?

Comment 5 Fedora End Of Life 2015-05-29 12:17:59 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 6 Fedora End Of Life 2015-06-29 21:28:29 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.