Version-Release number of selected component: 0ad-0.0.12-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/pyrogenesis crash_function: dir_watch_Add executable: /usr/bin/pyrogenesis kernel: 3.7.7-201.fc18.x86_64 uid: 1000 var_log_messages: Feb 17 23:13:25 fedora18 abrt[4742]: Saved core dump of pid 4729 (/usr/bin/pyrogenesis) to /var/spool/abrt/ccpp-2013-02-17-23:13:25-4729 (53993472 bytes) Truncated backtrace: Thread no. 1 (8 frames) #1 dir_watch_Add at ../../../source/lib/sysdep/os/linux/dir_watch_inotify.cpp:210 #2 vfs_Populate at ../../../source/lib/file/vfs/vfs_populate.cpp:186 #3 vfs_Lookup at ../../../source/lib/file/vfs/vfs_lookup.cpp:84 #4 VFS::GetFileInfo at ../../../source/lib/file/vfs/vfs.cpp:84 #5 CConfigDB::Reload at ../../../source/ps/ConfigDB.cpp:339 #6 CONFIG_Init at ../../../source/ps/GameSetup/Config.cpp:211 #7 Init at ../../../source/ps/GameSetup/GameSetup.cpp:890 #8 RunGameOrAtlas at ../../../source/main.cpp:503
Created attachment 698693 [details] File: backtrace
Created attachment 698694 [details] File: cgroup
Created attachment 698695 [details] File: core_backtrace
Created attachment 698696 [details] File: dso_list
Created attachment 698697 [details] File: environ
Created attachment 698698 [details] File: limits
Created attachment 698699 [details] File: maps
Created attachment 698700 [details] File: open_fds
Created attachment 698701 [details] File: proc_pid_status
Can you easily reproduce the problem? Please post output of the command ls -l /usr/share/0ad/mods/public/ The error was caused by the call int wd = inotify_add_watch(inotifyfd, realpath(OsString(path).c_str(), resolved), IN_CREATE | IN_DELETE | IN_CLOSE_WRITE); with the realpath call resolving to /usr/share/0ad/mods/public/ and the call returning -1, what caused 0ad to fallback to attempt to attach to the debugger when handling the error and making the call kill(getpid(), SIGTRAP); that did not help much due to not running the game under gdb.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.