|Summary:||Python script aborted with Modules/gcmodule.c:240: update_refs: Assertion ... failed|
|Product:||[Fedora] Fedora||Reporter:||Milan Kerslager <milan.kerslager>|
|Component:||python||Assignee:||James Antill <james.antill>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Brock Organ <borgan>|
|Version:||4||CC:||katzj, lyle.lasheimok, t.matsuu|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-03-09 21:42:42 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Milan Kerslager 2005-10-26 18:04:39 UTC
Python scripts are aborted when executed on specific HW configuration (Celeron 500, 256MB RAM, Elite P6BAT-Me). When the disc has been moved to the another machine (Athlon 750), all went ok. This up-to-date FC4 with python-2.4.1-2. Affected scripts are yum and printconf-backend (others possible too). The error message is: python: Modules/gcmodule.c:240: update_refs: Assertion `gc->gc.gc_refs == (-3)' failed. Aborted After some googling this seems like Python bug. Also I saw similar errors with a little bit different component than update_refs.
Comment 1 Seth Vidal 2005-11-29 16:22:56 UTC
Something similar seen when using the program quod-libet http://www.sacredchao.net/quodlibet/ticket/364 It looks like the same problem there as above.
Comment 2 Jeremy Katz 2007-01-06 21:14:20 UTC
Does this still happen?
Comment 3 petrosyan 2008-03-09 21:42:42 UTC
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.
Comment 4 Takanori MATSUURA 2008-04-01 07:22:51 UTC
I think buf 404911, bug 384221 and bug 408341 are the dupulication of this bug. In bug 384221 comment #5, it's not the python side but other side (means Fedora?) bug. I also got this message by using other python-based program. This bug should be reopend and we need to collect more information.
Comment 5 Lyle Lasheimok 2008-04-03 08:45:22 UTC
Hi all! :) Gimmie started to crash with that error message in Fedora 8, and still crashes in Fedora 9 Beta (bug 384221 mentioned above). In bug 404911 a Python developer says it's unlikely to be a Python problem, unless that crash can be reproduced with pure Python code. I'd like to help if more information are needed, but I'm not a Python programmer, so my debugging abilities are limited.
Comment 6 Takanori MATSUURA 2008-04-07 09:11:29 UTC
Hi James, Do I need to open the new bug for this? Hi Lyle, Can you install debuginfo packages? # debuginfo-install gimmie $ ulimit -c unlimited $ gimmie $ script $ gdb /usr/bin/python core.xxxxxx (gdb) where (edb) exit $ exit If you got a message like run debuginfo-install foo-debuginfo bar-debuginfo... when running gdb, run # debuginfo-install foo-debuginfo bar-debuginfo... and rerun the commands above from "$ script" to "$ exit". And attach the file "tpescript" here. I can't follow the file but assigner must understand it.
Comment 7 Lyle Lasheimok 2008-04-08 14:50:40 UTC
Created attachment 301646 [details] gdb output Thank you for the detailed instructions. :) Attached is a file which shows the output of gdb, using Fedora 9 Beta. I couldn't install all of the debuginfo packages, as that caused gdb to segfault. (I guess I need to repeat the procedure with gdb and file a separate bug report. :) ) Maybe it's already enough information, though, even with some of the packages missing. Thank you for all the help! :)