Bug 677051

Created attachment 478410 [details]
File: backtrace

I'm going to dish this over to python for the moment, but it could be lower in the stack than python, too.

David?

Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running this command:
  rpm -qa python python-libs rpm-python pygpgme yum-metadata-parser

Looking at the backtrace, it looks like the problem occurred in the program's single thread in _PyType_Lookup.

I post-processed the gdb backtrace, giving a rough python-level backtrace that looks like this:
  #4 /usr/lib/python2.7/site-packages/yum/sqlitesack.py:1362 searchPrco
  #9 /usr/lib/python2.7/site-packages/yum/sqlitesack.py:46 newFunc
  #13 /usr/lib/python2.7/site-packages/yum/sqlitesack.py:1400 searchProvides
  #23 /usr/lib/python2.7/site-packages/yum/packageSack.py:598 _computeAggregateListResult
  #27 /usr/lib/python2.7/site-packages/yum/packageSack.py:426 searchProvides
  #30 /usr/lib/python2.7/site-packages/yum/__init__.py:2990 returnPackagesByDep
  #33 /usr/lib/python2.7/site-packages/yum/__init__.py:3313 install
  #37 /usr/sbin/yum-complete-transaction:199 main
  #40 /usr/sbin/yum-complete-transaction:118 __init__
  #51 /usr/sbin/yum-complete-transaction:256 <module>
where the leading numbers are the C-level frame numbers from gdb.

I notice that the SIGSEGV location was at 0x4d2ade0a:
  eip            0x4d2ade0a	0x4d2ade0a <_PyType_Lookup+10>
but this location is halfway through an instruction within the machine code (as reported by the assembler dump):
   0x4d2ade06 <+6>:	call   0x4d24aa59 <__i686.get_pc_thunk.bx>
   0x4d2ade0b <+11>:	add    $0xdbd01,%ebx

BTW, comment #0 contains this text:
> Attached file: coredump, 39882752 bytes
but I don't see a coredump, just a backtrace.

In the top stack frames, the interpreter is looking up the "cursor" attribute of a <sqlite3.Connection> instance.

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Hi all,
      In my circumstance, I have switched over to Gentoo now, so I wouldn't think the bug will affect me. Thank you

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.