URL:
<http://gna.org/bugs/?11910>
Summary: Calling Py_Finalize in ai_python's destructor
causes segfault
Project: Battle for Wesnoth
Submitted by: oracle
Submitted on: Friday 06/27/2008 at 10:08
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Artificial Intelligence
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 1.5.1-svn
Operating System: linux
_______________________________________________________
Details:
Calling Py_Finalize in ai_python's destructor causes segfaults. I added code
to decref the builtin wesnoth module and this did help. It changed frequency
from every additional Py_Initialize call to about every third or fourth call.
Despite the module decref change, it still crashes. This likely means we
either have dangling pointers or are leaking memory via the existing python
interface.
Regardless some additional time needs to be spent looking at the python
interface to determine why Py_Finalize can not be safely called. Crashes
during Py_Initialize or Py_Finalize normally means something naughty is going
on.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?11910>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
