Update of bug #16845 (project wesnoth):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #5:
I don't think this happens in the official 1.9.x windows builds? I'm not sure
if I tested one since you reported this bug.
Anyways marking as Need Info since I don't have the proper setup to develop
Wesnoth under Windows, and I'm extremely busy.
The issue (from memory, I checked on this a while ago) seems to be that I run
a search for some other moves in the wb::move destructor. From the details you
give me, the move seems to get a shared pointer to itself in that search,
triggering the infinite deletion recursion when the pointer goes out of scope,
but it shouldn't get that shared pointer in the first place since he's just
been deleted from the action vector where I run the search. And under linux it
runs as expected.
I really need a windows coder who knows boost and smart pointers well to step
up and help with this.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?16845>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs