Bug 1005166 - [abrt] 0ad-0.0.14-1.fc19: exit: Process /usr/bin/pyrogenesis was killed by signal 11 (SIGSEGV)
Summary: [abrt] 0ad-0.0.14-1.fc19: exit: Process /usr/bin/pyrogenesis was killed by si...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: 0ad
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paulo Andrade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5355eb4e332f8bc3c72f09d0c9f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 10:44 UTC by Bastiaan Jacques
Modified: 2014-11-03 18:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-03 18:23:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (28.58 KB, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: cgroup (140 bytes, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: core_backtrace (3.92 KB, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: dso_list (8.21 KB, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: exploitable (82 bytes, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-06 10:44 UTC, Bastiaan Jacques
no flags Details
File: maps (43.01 KB, text/plain)
2013-09-06 10:45 UTC, Bastiaan Jacques
no flags Details
File: proc_pid_status (936 bytes, text/plain)
2013-09-06 10:45 UTC, Bastiaan Jacques
no flags Details

Description Bastiaan Jacques 2013-09-06 10:44:15 UTC
Description of problem:
loaded old savegame

Version-Release number of selected component:
0ad-0.0.14-1.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/pyrogenesis
crash_function: exit
environ:        
executable:     /usr/bin/pyrogenesis
kernel:         3.10.9-200.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
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

Comment 1 Bastiaan Jacques 2013-09-06 10:44:24 UTC
Created attachment 794654 [details]
File: backtrace

Comment 2 Bastiaan Jacques 2013-09-06 10:44:30 UTC
Created attachment 794655 [details]
File: cgroup

Comment 3 Bastiaan Jacques 2013-09-06 10:44:35 UTC
Created attachment 794656 [details]
File: core_backtrace

Comment 4 Bastiaan Jacques 2013-09-06 10:44:38 UTC
Created attachment 794657 [details]
File: dso_list

Comment 5 Bastiaan Jacques 2013-09-06 10:44:42 UTC
Created attachment 794658 [details]
File: exploitable

Comment 6 Bastiaan Jacques 2013-09-06 10:44:45 UTC
Created attachment 794659 [details]
File: limits

Comment 7 Bastiaan Jacques 2013-09-06 10:45:05 UTC
Created attachment 794660 [details]
File: maps

Comment 8 Bastiaan Jacques 2013-09-06 10:45:09 UTC
Created attachment 794661 [details]
File: proc_pid_status

Comment 9 Paulo Andrade 2014-11-03 15:23:38 UTC
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.

Comment 10 Bastiaan Jacques 2014-11-03 18:23:46 UTC
(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.


Note You need to log in before you can comment on or make changes to this bug.