MantisBT - VCMI
View Issue Details
0001765VCMIAI - Battlespublic2014-03-28 15:482022-03-16 17:24
KroArtem 
Tow 
normalminorhave not tried
closedunable to reproduce 
x86_64Ubuntu13.10
0.95 
 
0001765: AI crashed during battle, autofight turned on
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)
No tags attached.
Issue History
2014-03-28 15:48KroArtemNew Issue
2014-03-28 15:48KroArtemStatusnew => assigned
2014-03-28 15:48KroArtemAssigned To => Tow
2022-03-16 17:24PovelitelNote Added: 0008133
2022-03-16 17:24PovelitelStatusassigned => closed
2022-03-16 17:24PovelitelResolutionopen => unable to reproduce

Notes
(0008133)
Povelitel   
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.