0001765: AI crashed during battle, autofight turned on

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001765

VCMI

AI - Battles

public

2014-03-28 15:48

2022-03-16 17:24

Reporter

KroArtem

Assigned To

Tow

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

unable to reproduce

Platform

x86_64

Ubuntu

OS Version

13.10

Product Version

0.95

Target Version

Fixed in Version

Summary

0001765: AI crashed during battle, autofight turned on

Description

I was playing a battle, opponents creature was at the top left corner, some of my creatures were in the left middle and also there was a lake or something, so in theory my creatures were able to reach them but path was blocked. At this time this crash happened. Yep, it was auto fighting.

Probably it's not related to crash but there was nothing unusual in server_log and client_log.


Opening StupidAI
Loaded Stupid AI 0.1
[New Thread 0x7fffe1a4e700 (LWP 29929)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe1a4e700 (LWP 29929)]
0x00007fffe1047f74 in CStupidAI::activeStack (this=0x7fffacdf56f8, stack=0x0)
    at /build/buildd/vcmi-0.95+svn3519~ubuntu13.10.1/AI/StupidAI/StupidAI.cpp:100
100 /build/buildd/vcmi-0.95+svn3519~ubuntu13.10.1/AI/StupidAI/StupidAI.cpp: Нет такого файла или каталога.
(gdb) bt
#0 0x00007fffe1047f74 in CStupidAI::activeStack (this=0x7fffacdf56f8,
    stack=0x0)
    at /build/buildd/vcmi-0.95+svn3519~ubuntu13.10.1/AI/StupidAI/StupidAI.cpp:100
#1 0x000000000056eb3b in operator() (__closure=0x7fffdbbfe938)
    at /build/buildd/vcmi-0.95+svn3519~ubuntu13.10.1/client/battle/CBattleInterface.cpp:2845
0000002 boost::detail::thread_data<CBattleInterface::requestAutofightingAIToTakeAction()::__lambda22>::run(void) (this=0x7fffdbbfe780)
    at /usr/include/boost/thread/detail/thread.hpp:117
0000003 0x00007ffff6a9a94a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.53.0
0000004 0x00007ffff6879f6e in start_thread (arg=0x7fffe1a4e700)
    at pthread_create.c:311
0000005 0x00007ffff3d6d9cd in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
(gdb)

Tags

No tags attached.

Attached Files

Relationships

Notes
(0008133) Povelitel (updater) 2022-03-16 17:24	Guys, I will close this bug after the statute of limitations expires. It cannot be reproduced. It's probably already been fixed. But if the problem still exists, you can always open a new ticket.

Issue History
Date Modified	Username	Field	Change
2014-03-28 15:48	KroArtem	New Issue
2014-03-28 15:48	KroArtem	Status	new => assigned
2014-03-28 15:48	KroArtem	Assigned To	=> Tow
2022-03-16 17:24	Povelitel	Note Added: 0008133
2022-03-16 17:24	Povelitel	Status	assigned => closed
2022-03-16 17:24	Povelitel	Resolution	open => unable to reproduce

Site | Forums | Wiki | Slack | GitHub