Red Hat Bugzilla – Bug 1005166
[abrt] 0ad-0.0.14-1.fc19: exit: Process /usr/bin/pyrogenesis was killed by signal 11 (SIGSEGV)
Last modified: 2014-11-03 13:23:46 EST
Description of problem:
loaded old savegame
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#3 exit at exit.c:99
#4 try_gui_display_error at ../../../source/lib/sysdep/os/unix/unix.cpp:151
#5 sys_display_error at ../../../source/lib/sysdep/os/unix/unix.cpp:211
#6 CallDisplayError at ../../../source/lib/debug.cpp:378
#7 debug_DisplayError at ../../../source/lib/debug.cpp:469
#8 debug_OnError at ../../../source/lib/debug.cpp:546
#9 VFS::GetDirectoryEntries at ../../../source/lib/file/vfs/vfs.cpp:105
#10 vfs::GetPathnames at ../../../source/lib/file/vfs/vfs_util.cpp:43
#11 CAIWorker::CAIPlayer::LoadScripts at ../../../source/simulation2/components/CCmpAIManager.cpp:196
#12 CAIWorker::CAIPlayer::Initialise at ../../../source/simulation2/components/CCmpAIManager.cpp:211
Created attachment 794654 [details]
Created attachment 794655 [details]
Created attachment 794656 [details]
Created attachment 794657 [details]
Created attachment 794658 [details]
Created attachment 794659 [details]
Created attachment 794660 [details]
Created attachment 794661 [details]
Sorry for the delay responding.
Do you recall if the crash cause was loading a saved game?
Did you see the "xmessage" emergency window before exit?
It was showing this message at crash time:
"Function call failed: return value was -110100 (VFS directory not found)"
but did not gracefuly quit after that.
(In reply to Paulo Andrade from comment #9)
> Sorry for the delay responding.
> Do you recall if the crash cause was loading a saved game?
I don't recall, but I noted that it was loading a savegame in the problem description in my original report.
> Did you see the "xmessage" emergency window before exit?
I can't remember.
The old savegames don't load at all with the current version of 0ad (a warning dialogue is shown, then an exception is thrown when the map turns out to be incompatible). So I think it would be best to close this issue until and if the problem occurs again.