MetaKit crash
Damn ... maybe compacting the database wasn't such a good idea ... ???
I've set up a script to supervise the PyCS process and restart it (then e-mail me some log snippets) if it goes down. Fingers crossed - let's see how this goes.
... more like this: [MetaKit, Python Community Server]
-su-2.05b$ gdb -c python2.2.core /pycs/bin/python2.2
GNU gdb 4.18 (FreeBSD)
[...]
This GDB was configured as "i386-unknown-freebsd"...[...]
Core was generated by `python2.2'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libc_r.so.4...done.
[...]
#0 0x281889e8 in memcpy () from /usr/lib/libc_r.so.4
(gdb) bt
#0 0x281889e8 in memcpy () from /usr/lib/libc_r.so.4
#1 0xca01259 in ?? ()
#2 0x283d4d0b in c4_FormatB::Define () from /pycs/lib/python2.2/site-packages/Mk4py.so
#3 0x283d9a6c in c4_HandlerSeq::Prepare () from /pycs/lib/python2.2/site-packages/Mk4py.so
#4 0x283d6912 in c4_FormatV::SetupAllSubviews () from /pycs/lib/python2.2/site-packages/Mk4py.so
#5 0x283d7186 in c4_FormatV::HasSubview () from /pycs/lib/python2.2/site-packages/Mk4py.so
#6 0x283d92b7 in c4_HandlerSeq::Restructure () from /pycs/lib/python2.2/site-packages/Mk4py.so
#7 0x283d8ea6 in c4_HandlerSeq::DetachFromParent () from /pycs/lib/python2.2/site-packages/Mk4py.so
#8 0x283d8c09 in c4_HandlerSeq::~c4_HandlerSeq () from /pycs/lib/python2.2/site-packages/Mk4py.so
#9 0x283eaee8 in c4_Sequence::DecRef () from /pycs/lib/python2.2/site-packages/Mk4py.so
#10 0x283e4bc5 in c4_Storage::~c4_Storage () from /pycs/lib/python2.2/site-packages/Mk4py.so
#11 0x283a2e31 in c4_PyStream::Write () from /pycs/lib/python2.2/site-packages/Mk4py.so
#12 0x80c4580 in dict_dealloc (mp=0x86bf30c) at Objects/dictobject.c:703
#13 0x80ad273 in instance_dealloc (inst=0x86c33ec) at Objects/classobject.c:656
#14 0x80c428f in PyDict_SetItem (op=0x86bf10c, key=0x81d6500, value=0x80e085c) at Objects/dictobject.c:373
#15 0x80c7061 in _PyModule_Clear (m=0x86c330c) at Objects/moduleobject.c:136
#16 0x808b227 in PyImport_Cleanup () at Python/import.c:352
#17 0x8094189 in Py_Exit (sts=0) at Python/pythonrun.c:218
#18 0x80931fe in handle_system_exit () at Python/pythonrun.c:838
#19 0x8093257 in PyErr_PrintEx (set_sys_last_vars=1) at Python/pythonrun.c:852
#20 0x8094124 in PyErr_Print () at Python/pythonrun.c:778
#21 0x8092dcd in PyRun_SimpleFileExFlags (fp=0x281ab240, filename=0xbfbffd50 "/home/pycs/usr/lib/pycs/bin/pycs.py",
closeit=1, flags=0xbfbffc08) at Python/pythonrun.c:677
#22 0x8093c08 in PyRun_AnyFileExFlags (fp=0x281ab240, filename=0xbfbffd50 "/home/pycs/usr/lib/pycs/bin/pycs.py", closeit=1,
flags=0xbfbffc08) at Python/pythonrun.c:483
#23 0x8052a74 in Py_Main (argc=2, argv=0xbfbffc80) at Modules/main.c:367
#24 0x8052374 in main (argc=2, argv=0xbfbffc80) at Modules/python.c:10
#25 0x80522d1 in _start ()
I've set up a script to supervise the PyCS process and restart it (then e-mail me some log snippets) if it goes down. Fingers crossed - let's see how this goes.