[Wesnoth-bugs] [bug #25227] assertion failure when normal/planned moves conflict

2016-11-07 Thread Wedge009
Follow-up Comment #4, bug #25227 (project wesnoth):

Bug #20352 seems related, has the same assertion failure in erase().

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs


[Wesnoth-bugs] [bug #25227] assertion failure when normal/planned moves conflict

2016-10-26 Thread Wedge009
Update of bug #25227 (project wesnoth):

  Status:None => Confirmed  
Operating System:   linux => All

___

Follow-up Comment #3:

I managed to reliably replicate the assertion failure when the divergent
planned moves go up to 5 turns ahead or more (Windows and Linux).
Interestingly, if I ignore the assertion failure in Windows I don't appear to
have any further problems even after exiting the game.

But I think anything that happens after the assertion failure - normal or
otherwise - is probably due to the memory getting corrupted or staying intact,
which would probably be non-deterministic, especially between different
operating systems and compilations.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs


[Wesnoth-bugs] [bug #25227] assertion failure when normal/planned moves conflict

2016-10-25 Thread Matthias Krüger
Follow-up Comment #2, bug #25227 (project wesnoth):

Your reproducing description sounds about right to me and I was able to
reproduce the assertion failure and heap use after free with that. I don't
understand why it doesn't crash though :/

(file #29148)
___

Additional Item Attachment:

File name: use_after_free_conflicting_planningmode_and_movement.log Size:50 KB


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs


[Wesnoth-bugs] [bug #25227] assertion failure when normal/planned moves conflict

2016-10-24 Thread Wedge009
Follow-up Comment #1, bug #25227 (project wesnoth):

From what you describe, it sounds like this is a problem. However, I can't
replicate the issue.

I have a unit starting at hex A. I make a move which requires several turns:
it moves to hex B for this turn, and will move to hex C in the next turn.

Before ending my turn, I plan some moves where it will go to hex D instead of
hex C in the next turn. Upon ending my turn and going to the next turn, the
unit goes to hex C and the planned move to hex D is invalid, so the planned
moves are discarded. I confirm that turn_of_position is zero when this happens
too.

It doesn't seem to make a difference when I make the planned moves diverge
later, eg the planned move as well as the regular move goes to hex C, but then
the regular and planned moves diverge after that - the planned moves just
become invalid (and are thus removed) when that happens.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs


[Wesnoth-bugs] [bug #25227] assertion failure when normal/planned moves conflict

2016-10-24 Thread Matthias Krüger
URL:
  

 Summary: assertion failure when normal/planned moves conflict
 Project: Battle for Wesnoth
Submitted by: matthiaskrgr
Submitted on: Mon 24 Oct 2016 14:00:32 UTC
Category: Bug
Severity: 3 - Normal
Priority: 5 - Normal
  Item Group:  None of the others
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: v1.13.5+dev (f4870a8-Clean)
Operating System: linux

___

Details:

Have unit
Also make a regular movement lasting severl turns to some hex on the map.
Enter planning mode, make a planned movement to some other hex in planning
mode.

End turn.
=> on the next turn of that unit, the game will crash:

wesnoth:
/home/matthias/vcs/github/wesnoth/src/whiteboard/side_actions.cpp:228:
wb::side_actions_container::iterator
wb::side_actions_container::erase(wb::side_actions_container::iterator):
Assertion `turn_of_position == 0' failed.


Might be related: https://gna.org/bugs/index.php?25222




___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs