Bug 669033

Summary: something fishy with argument parsing
Product: [Fedora] Fedora Reporter: Curtis Doty <curtis>
Component: cronologAssignee: Ken Dreyer <ktdreyer>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jafo-redhat
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-06-27 12:36:39 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:

Description Curtis Doty 2011-01-12 14:20:07 UTC
Instead of showing the error, it segfaults:

$ cronolog --prev=prev curr       
Segmentation fault

Short opts work, however:

$ cronolog -P prev curr      
A current log symlink is needed to mantain a symlink to the previous log

Here's the backtrace:

#0  __strncmp_sse2 () at ../sysdeps/x86_64/strcmp.S:106
#1  0x000000326c6c6aa6 in _getopt_internal_r (argc=3, argv=0x7fffffffe0a8, optstring=0x402a76 "ad:eop:s:z:H:P:S:l:hVx:", longopts=0x604340, longind=0x0, long_only=0, 
    d=0x326c97aee0, posixly_correct=0) at getopt.c:542
#2  0x000000326c6c7b0b in _getopt_internal (argc=<value optimized out>, argv=<value optimized out>, optstring=<value optimized out>, longopts=<value optimized out>, 
    longind=<value optimized out>, long_only=<value optimized out>, posixly_correct=0) at getopt.c:1131
#3  0x000000326c6c7bf3 in getopt_long (argc=<value optimized out>, argv=<value optimized out>, options=<value optimized out>, long_options=<value optimized out>, 
    opt_index=<value optimized out>) at getopt1.c:66
#4  0x000000000040118a in main (argc=3, argv=0x7fffffffe0a8) at cronolog.c:174

Comment 1 Bug Zapper 2011-05-30 11:58:52 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora Admin XMLRPC Client 2011-06-21 18:29:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Ken Dreyer 2011-06-23 01:41:07 UTC
"cronolog --prev=prev curr" does not segfault for me on Fedora 14, i686. Maybe a 64-bit specific bug? Please update the version number if you're still experiencing the problem.

Comment 4 Bug Zapper 2011-06-27 12:36:39 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Thank you for reporting this bug and we are sorry it could not be fixed.