Bug 797528

Summary: python: double free or corruption
Product: [Fedora] Fedora Reporter: Herbert Carl Meyer <hcmeyer>
Component: PyQt4Assignee: Rex Dieter <rdieter>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dmalcolm, rdieter, than
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: 2013-02-13 21:30:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
console error messages none

Description Herbert Carl Meyer 2012-02-26 15:22:10 UTC
Created attachment 565900 [details]
console error messages

Description of problem:
python errors out,  in libQt4Core, with core dump, when trying to run program

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

python 2.7.2, PyQt4

How reproducible:

100%

Steps to Reproduce:

1. try to run a particular program under development,
started by name from command line.

2.
3.
  
Actual results:
python aborts with double free or corruption message, and core dumped

Expected results:
program execution, or python syntax or other error message


Additional info:

console output attached

Comment 1 Herbert Carl Meyer 2012-02-26 17:09:49 UTC
real "cause" is missing () on program line "while self.recentFiles.count > 9", which causes self.recentFiles.takeLast() to be called on empty list.

However, this should cause python or qt to produce error message or exception, not dump core.

Comment 2 Than Ngo 2012-02-27 16:01:43 UTC
(In reply to comment #1)
> real "cause" is missing () on program line "while self.recentFiles.count > 9",
> which causes self.recentFiles.takeLast() to be called on empty list.
> 
> However, this should cause python or qt to produce error message or exception,
> not dump core.

could you please attach an small testcase to reproduce this crash?

thanks

Comment 3 Herbert Carl Meyer 2012-02-27 20:24:48 UTC
I will try, the two lines are in a 1800 line program. I will see if a simple test case triggers the error.

Comment 4 Fedora End Of Life 2013-01-16 17:08:39 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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 5 Fedora End Of Life 2013-02-13 21:30:59 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.