[Python-bugs-list] [Bug #110870] Coredump in moduleobjectc.c:134 (PR#79)

[noreply@sourceforge.net]

Bug #110870, was updated on 2000-Aug-01 14:42
Here is a current snapshot of the bug.

Project: Python
Category: Modules
Status: Open
Resolution: None
Bug Group: 3rd Party
Priority: 5
Summary: Coredump in moduleobjectc.c:134 (PR#79)

Details: Jitterbug-Id: 79
Submitted-By: ajung@sz-sb.de
Date: Mon, 13 Sep 1999 07:29:09 -0400 (EDT)
Version: 1.5.2
OS: Solaris 2.6/Sparc


(ojs@bonnie:~/PROD/lib/site-python/ojs) 73 : !gdb
gdb python core
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (sparc-sun-solaris2.4), Copyright 1996 Free Software Foundation,
Inc...
Core was generated by `python -v prod_descr.py'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libsocket.so.1...done.
Reading symbols from /usr/lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libdl.so.1...done.
Reading symbols from /usr/lib/libm.so.1...done.
Reading symbols from /usr/lib/libc.so.1...done.
Reading symbols from /usr/lib/libmp.so.2...done.
Reading symbols from
/usr/platform/SUNW,Ultra-Enterprise/lib/libc_psr.so.1...done.
Reading symbols from
/ojs/home/ojs/PROD/lib/python1.5/site-packages/DateTime/mxDateTime/mxDateTime.so...done.
#0  0x49220 in _PyModule_Clear (m=0xc76e4) at moduleobject.c:134
134                     if (value != Py_None && PyString_Check(key)) {
(gdb) bt
#0  0x49220 in _PyModule_Clear (m=0xc76e4) at moduleobject.c:134
#1  0x29fe4 in PyImport_Cleanup () at import.c:308
#2  0x30d18 in Py_Finalize () at pythonrun.c:206
#3  0x21c8c in Py_Main (argc=3, argv=0xeffff964) at main.c:298
#4  0x216e4 in main (argc=3, argv=0xeffff964) at python.c:12


I get the traceback above from a small module that
contains just 2 import statements. One module contains just
the declaration of 2 classes and the second module contains some
dicts,lists...nothing special. When I change the order of both import
statements in the main script no core dump occurs.

Any idea ?

Andreas 


====================================================================
Audit trail:
Wed Sep 15 23:50:12 1999	guido	changed notes
Wed Sep 15 23:50:12 1999	guido	moved from incoming to irreproducible
Thu Sep 16 10:15:31 1999	guido	changed notes
Thu Sep 16 10:15:32 1999	guido	moved from irreproducible to 3rdpartybug

Follow-Ups:

Date: 2000-Aug-01 14:42
By: none

Comment:
From: Guido van Rossum <guido@CNRI.Reston.VA.US>
Subject: Re: [Python-bugs-list] Coredump in moduleobjectc.c:134 (PR#79)
Date: Thu, 16 Sep 1999 10:04:18 -0400

> I was able to get more information. The problem might occur with the following code:
> 
> * module.py*
> 
> from prod_support import read_current_prodids
> 
> PRODIDS = read_current_prodids()
> 
> 
> * main.py *
> 
> import module.py
> 
> 
> When I run python on main.py I get the bus error. When I switch module.py to:
> 
> import prod_support
> PRODIDS = prod_support.read_current_prodids()
> 
> everything is ok. The function read_current_prodids() uses DCOracle (Digicool/Zope).
> I'm not sure if this causes the problem - I'll try to figure it out.

Probably something in the prod_support module causes the problem.  I'm 
quite sure the problem is not in Python itself, so the Python bugs
list is not the place to report the bug.

--Guido van Rossum (home page: http://www.python.org/~guido/)

-------------------------------------------------------

Date: 2000-Aug-01 14:42
By: none

Comment:
Probably caused by DCOracle or other 3rd party extension.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110870&group_id=5470