core dump during test_array for Python.2.0b1
Art Haas
arthur.haas at westgeo.com
Wed Sep 6 16:26:55 EDT 2000
Hi.
I'm trying out the latest and greatest version, and get a core dump
when running the `test_array' test.
I'm running on Linux, i686 (Redhat-6.2).
Here's a little info courtesy of gdb.
(gdb) where
#0 0x0 in ?? ()
#1 0x4019616a in array_dealloc (op=0x8136e30) at ./arraymodule.c:449
#2 0x80575ba in eval_code2 (co=0x8119ff0, globals=0x816e944, locals=0x0,
args=0x816a5bc, argcount=2, kws=0x816a5c4, kwcount=0, defs=0x0,
defcount=0, owner=0x0) at ceval.c:1550
#3 0x8057e54 in eval_code2 (co=0x8199b90, globals=0x816e944, locals=0x0,
args=0x8141568, argcount=0, kws=0x8141568, kwcount=0, defs=0x0,
defcount=0, owner=0x0) at ceval.c:1828
#4 0x8057e54 in eval_code2 (co=0x81196e8, globals=0x816e944,
locals=0x816e944, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
defcount=0, owner=0x0) at ceval.c:1828
#5 0x8054e75 in PyEval_EvalCode (co=0x819a160, globals=0x816e944,
locals=0x816e944) at ceval.c:330
#6 0x8063637 in PyImport_ExecCodeModuleEx (name=0xbfffef30 "test_array",
co=0x819a160, pathname=0xbfffe630 "./Lib/test/test_array.pyc")
at import.c:488
#7 0x8063b7a in load_source_module (name=0xbfffef30 "test_array",
pathname=0xbfffeaa0 "./Lib/test/test_array.py", fp=0x8119da8)
at import.c:721
#8 0x80643ad in load_module (name=0xbfffef30 "test_array", fp=0x8119da8,
buf=0xbfffeaa0 "./Lib/test/test_array.py", type=1) at import.c:1190
#9 0x80650a3 in import_submodule (mod=0x80ce4ec,
subname=0xbfffef30 "test_array", fullname=0xbfffef30 "test_array")
at import.c:1718
#10 0x8064c5a in load_next (mod=0x80ce4ec, altmod=0x80ce4ec,
p_name=0xbffff360, buf=0xbfffef30 "test_array", p_buflen=0xbfffef2c)
at import.c:1574
#11 0x806487c in import_module_ex (name=0x0, globals=0x80e3844,
locals=0x81415a4, fromlist=0x811bcdc) at import.c:1425
#12 0x8064a03 in PyImport_ImportModuleEx (name=0x814492c "test_array",
globals=0x80e3844, locals=0x81415a4, fromlist=0x811bcdc) at import.c:1466
#13 0x809f2b5 in builtin___import__ (self=0x0, args=0x81660e4)
at bltinmodule.c:34
#14 0x8058ed0 in call_builtin (func=0x80dfc80, arg=0x81660e4, kw=0x0)
at ceval.c:2628
#15 0x8058d59 in PyEval_CallObjectWithKeywords (func=0x80dfc80, arg=0x81660e4,
kw=0x0) at ceval.c:2596
#16 0x8057c18 in eval_code2 (co=0x8100188, globals=0x80e3844, locals=0x0,
args=0x81409c8, argcount=5, kws=0x81409dc, kwcount=0, defs=0x813ec10,
defcount=1, owner=0x0) at ceval.c:1929
#17 0x8057e54 in eval_code2 (co=0x8179c98, globals=0x80e3844, locals=0x0,
args=0x80edcfc, argcount=0, kws=0x80edcfc, kwcount=0, defs=0x8174bb0,
defcount=10, owner=0x0) at ceval.c:1828
#18 0x8057e54 in eval_code2 (co=0x81342e0, globals=0x80e3844,
locals=0x80e3844, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
defcount=0, owner=0x0) at ceval.c:1828
#19 0x8054e75 in PyEval_EvalCode (co=0x8179b50, globals=0x80e3844,
locals=0x80e3844) at ceval.c:330
#20 0x806a4e9 in run_node (n=0x80ec278,
filename=0xbffff96b "./Lib/test/regrtest.py", globals=0x80e3844,
locals=0x80e3844) at pythonrun.c:886
#21 0x8069914 in PyRun_SimpleFileEx (fp=0x80df848,
filename=0xbffff96b "./Lib/test/regrtest.py", closeit=1) at pythonrun.c:579
#22 0x80518a4 in Py_Main (argc=4, argv=0xbffff7f4) at main.c:265
#23 0x400a69cb in __libc_start_main (main=0x80514b0 <main>, argc=4,
argv=0xbffff7f4, init=0x805096c <_init>, fini=0x80b816c <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffff7ec)
at ../sysdeps/generic/libc-start.c:92
(gdb) frame 1
#1 0x4019616a in array_dealloc (op=0x8136e30) at ./arraymodule.c:449
449 PyMem_DEL(op->ob_item);
(gdb) p *op
$3 = {ob_refcnt = 0, ob_type = 0x4019a960, ob_size = 15,
ob_item = 0x816b730 "ccThe quick abc\b\030", ob_descr = 0x40199760}
The pointer isn't null, but it looks like things die in the free() call.
The array module is built as a shared module, if this makes a difference.
Anyone else seeing this???
--
###############################
# Art Haas
# (713) 689-2417
###############################
More information about the Python-list
mailing list