[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

2015-04-16 Thread Piotr Wajnberg
Additional Item Attachment, bug #23488 (project wesnoth): File name: debug3.log Size:5 KB File name: debug4.log Size:7 KB File name: debug.val Size:700 KB ___ Reply to this item

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

2015-04-16 Thread Piotr Wajnberg
Follow-up Comment #8, bug #23488 (project wesnoth): After recompiling with just vanilla flags (-O2) I've still managed to get two different crashes in 3p survival. I'm also attaching output from valgrind from a normal run (very slow so not practical to repeat many times) in case it proves useful.

[Wesnoth-bugs] [bug #23490] Side specific variables

2015-04-16 Thread anonymous
URL: Summary: Side specific variables Project: Battle for Wesnoth Submitted by: None Submitted on: Do 16 Apr 2015 18:43:49 UTC Category: Feature Request Severity: 3 - Normal

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

2015-04-16 Thread anonymous
Follow-up Comment #9, bug #23488 (project wesnoth): I tried again to reproduce with 3p vs survival mp game with all sides beeing ai and still got no crash. Also i couldn't extract useful information from the valigrind file :( Does this crash happen most of the time or only rarely? __

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

2015-04-16 Thread Piotr Wajnberg
Additional Item Attachment, bug #23488 (project wesnoth): File name: final.debugSize:25 KB ___ Reply to this item at: ___ Message sent via/b

[Wesnoth-bugs] [bug #23488] All AI multiplayer crash

2015-04-16 Thread Piotr Wajnberg
Follow-up Comment #10, bug #23488 (project wesnoth): I'd say it happens rather rarely however I think I see a pattern here. Every time I've recompiled I got the crash on the first run and then couldn't see it on subsequent runs or had to try many times. To add another data point to this theory her

[Wesnoth-bugs] [bug #23462] Scenario ToD initially gets set to random time on start

2015-04-16 Thread Ignacio R. Morelle
Update of bug #23462 (project wesnoth): Severity: 4 - Important => 5 - Blocker ___ Follow-up Comment #1: Note that this may break scenario balance or throw scripted sequences out of order. ___

[Wesnoth-bugs] [bug #23462] Scenario ToD initially gets set to random time on start

2015-04-16 Thread Ignacio R. Morelle
Update of bug #23462 (project wesnoth): Item Group:Graphics => WML ___ Reply to this item at: ___ Message sent

[Wesnoth-bugs] [bug #23461] Shroud is applied incorrectly to next scenarios with none

2015-04-16 Thread Ignacio R. Morelle
Update of bug #23461 (project wesnoth): Severity: 4 - Important => 5 - Blocker ___ Reply to this item at: ___ Message sent

[Wesnoth-bugs] [bug #23475] documentate executing order of [event]

2015-04-16 Thread Rodrigo López Caruana
Follow-up Comment #7, bug #23475 (project wesnoth): I am right now relaying for 1.12 in [era] events being fired before [modification] ones. It looks both intuitive and usefull behavior. That is why I asked for documentate it, as long there is none "expected behavior", I can not ask for a bug fix