+++ This bug was initially created as a clone of Bug #614332 +++ abrt version: 1.1.5 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python /usr/bin/yum upgrade component: yum crash_function: _getopt_internal_r executable: /usr/bin/python global_uuid: 0f942e761185876465ab44914503bb3c9196013c kernel: 2.6.35-0.27.rc4.git0.fc14.x86_64 package: yum-3.2.27-17.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 4 (SIGILL) release: Fedora release 14 (Rawhide) time: 1279089410 uid: 0 --- Additional comment from mnowak on 2010-07-14 03:05:03 EDT --- Created an attachment (id=431686) File: backtrace --- Additional comment from mnowak on 2010-07-14 03:06:32 EDT --- I was just doing yum upgrade, suddenly process have died. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ abrt thought it's yum crash but it was python's. abrt should have found correct component.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is not a bug we blame the script for the python crashes, it's quite difficult to determine if the crash was caused by a bug in a python interpreter or by the script (yes, bad script can cause python to SEGV), but usually it's the script to blame for the crash, so that's why abrt blamed yum. Jirka