Seen this a few times, but didn't really look into it: Fatal Python error: PyThreadState_Get: no current thread
Now that I'm playing with gdb, I've got at least a stacktrace so that we can fix this. Seems somebody wants to use python after we already stopped the interpreter. Program received signal SIGABRT, Aborted. 0x90047dac in kill () (gdb) bt #0 0x90047dac in kill () #1 0x9012d7b4 in abort () #2 0x9837416c in Py_FatalError () #3 0x9837127c in PyThreadState_Get () #4 0x98364268 in PyErr_Fetch () #5 0x98337248 in _PyObject_SlotCompare () #6 0x9832c500 in PyType_GenericNew () #7 0x98329a5c in PyTuple_SetItem () #8 0x01304acc in world::mapview::~mapview (this=0x132195c) at ../../../adonthell/src/world/mapview.cc:77 #9 0x012fa354 in cxa_atexit_wrapper () #10 0x9001495c in __cxa_finalize () #11 0x90014844 in exit () #12 0x000075a0 in _start () #13 0x000072a0 in start () Mapview is the culprit! Will take a look at that eventually, unless somebody else is faster ... Kai _______________________________________________ Adonthell-devel mailing list Adonthell-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/adonthell-devel
