0001289: Game crashes when attacking peasants with rogues from below and behind (SE)

Notes
(0003621) Zamolxis (viewer) 2013-06-01 23:07	Which game version are you using? Please use the field Product Version for future reports so that we know where to look for it. FYI - I opened your map in VCMI 0.93 (released yesterday) and I am able to attack the Peasant with my Rogue from belor & behind. So it could be platform related (I'm on Win7), or different release, or maybe some actions you took before.

(0003622) krs (reporter) 2013-06-02 08:31	I am using 0.93. I could not enter it because it was too new and did not yet appear on version dropdown list, so I left it blank. I am on windows 7 with a fresh VCMI 0.93 install. Call Stack: http://pastebin.com/Bz6eGsJi [^] Server Log: http://pastebin.com/0nBrAyp1 [^] Partial Client Log: http://pastebin.com/GG8egtQr [^]

(0003624) Zamolxis (viewer) 2013-06-02 09:03	Thanks (and sorry about the comment on game version then - it must have been added soon after you created the report). But as I can't reproduce it, can you clarify the following: > You reported Reproducibility "have not tried". Did you try meanwhile? Is it always reproducible? > If it's reproducible, just to make sure I got this right, what you do is the following: - Start map and attack directly any of the Peasants below the starting hero? - In battle, Rogue & Peasant move towards each other, but when they're close enough, you first let the Peasant move closer to your Rogue, then move to attack it from the right hex below him?

(0003626) krs (reporter) 2013-06-02 10:42	It is 100% reproducible. (I forgot to fill that when I've submitted the report, saw that later, but I do not know how to change it.) No other actions. Just accept all the map messages, then on your turn attack any of the peasants below (take the middle). In battle it did not matter the order of the movements you made. To be 100% on the same page: Move rogues in front -> peasants move -> attack peasants from SE.

(0003632) Zamolxis (viewer) 2013-06-02 14:09	I updated Reproducibility to "Always" (can only be done by an admin or dev; that's why I also asked, as I suspected that's the case). To be on the same page, that's why I rephrased the position to "right hex below", to make sure that's what you mean by "SE" (I don't really express battlefield directions in cardinal points, as in a way they are 6, not 4 or 8). In other words, there are 2 hexes below and adjacent to the one of the Peasant, and I assume it's the one more on your right (or left-behind from Peasant's perspective), that you're referring to. If that's the one, then it's not reproducible for me. I'll let other devs check your logs if they see something, but otherwise what could help, besides the logs, is to attach a crashdump. If VCMI doesn't create one automatically in your game folder, can you force one by typing "crash" in the console when the issue happens?

(0003648) krs (reporter) 2013-06-03 07:18 edited on: 2013-06-03 07:18	I am runing VCMI from debug mode. How to save a crash? I tried typing crash in the window that does all the logging but it did not work.

(0003650) Tow (developer) 2013-06-03 09:07	> I am runing VCMI from debug mode. That is an important piece of information. I tried reproducing it with released build to no avail, then with debug build of trunk — and then it happened. By the way… by debug mode do you mean running a Debug build of VCMI or are you running release (RD configuration) build with a debugger attached? > How to save a crash? I tried typing crash in the window that does all the logging but it did not work. If you have debugger attached, then there is no need. Just capture call stacks and paste them. [Crashdumps basically store call stacks but they are not always readable.] It would be great if you not only captured the call stack for a thread that crash but also call stacks from other important threads. The important threads are: * GUIHandler::run * CClient::run

(0003654) radek (reporter) 2013-06-03 12:39 edited on: 2013-06-03 12:41	I have similar problem when attacking Rogues with Archangels. 100% reproducible. Release 0.93 on Arch. Steps to reproduce: Go with Caitlin to the nearest Rogues. Attack middle stack of Rogues with Archangels from tiles under Rogues (not form left or on a slant). Attachment: battle_crash.zip.

(0003658) krs (reporter) 2013-06-04 14:56	I forgot to check upon this lately sry. Yes I was running the whole thing in debug mode.I thought it did not matter if debug or release since it was the same version so I have not mentioned it. It seems it does.

(0008064) Povelitel (updater) 2022-03-14 21:50	Can anyone repeat this bug now?

(0008229) Povelitel (updater) 2022-03-28 18:22	I tried to reproduce. I didn't succeed. If anyone can reproduce, open again.

Issue History
Date Modified	Username	Field	Change
2013-06-01 22:07	krs	New Issue
2013-06-01 22:07	krs	File Added: after.h3m
2013-06-01 23:07	Zamolxis	Note Added: 0003621
2013-06-01 23:07	Zamolxis	Status	new => feedback
2013-06-02 08:31	krs	Note Added: 0003622
2013-06-02 08:31	krs	Status	feedback => new
2013-06-02 08:42	Ivan	Product Version	=> 0.93
2013-06-02 09:03	Zamolxis	Note Added: 0003624
2013-06-02 09:03	Zamolxis	Status	new => feedback
2013-06-02 10:42	krs	Note Added: 0003626
2013-06-02 10:42	krs	Status	feedback => new
2013-06-02 13:58	Zamolxis	Reproducibility	have not tried => always
2013-06-02 14:09	Zamolxis	Note Added: 0003632
2013-06-02 14:10	Zamolxis	Status	new => feedback
2013-06-03 07:18	krs	Note Added: 0003648
2013-06-03 07:18	krs	Status	feedback => new
2013-06-03 07:18	krs	Note Edited: 0003648	View Revisions
2013-06-03 09:07	Tow	Note Added: 0003650
2013-06-03 09:24	Tow	Assigned To	=> Tow
2013-06-03 09:24	Tow	Status	new => confirmed
2013-06-03 12:39	radek	Note Added: 0003654
2013-06-03 12:40	radek	File Added: battle_crash.zip
2013-06-03 12:41	radek	Note Edited: 0003654	View Revisions
2013-06-04 14:56	krs	Note Added: 0003658
2022-03-14 21:50	Povelitel	Note Added: 0008064
2022-03-14 21:50	Povelitel	Assigned To	Tow =>
2022-03-14 21:50	Povelitel	Status	confirmed => feedback
2022-03-28 18:22	Povelitel	Note Added: 0008229
2022-03-28 18:22	Povelitel	Status	feedback => closed
2022-03-28 18:22	Povelitel	Resolution	open => unable to reproduce

Relationships