Hide Forgot
Version-Release number of selected component: 0ad-0.0.20-4.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/pyrogenesis crash_function: try_gui_display_error executable: /usr/bin/pyrogenesis global_pid: 3806 kernel: 4.7.3-200.fc24.i686+PAE pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 try_gui_display_error at ../../../source/lib/sysdep/os/unix/unix.cpp:155 #5 sys_display_error at ../../../source/lib/sysdep/os/unix/unix.cpp:215 #6 CallDisplayError at ../../../source/lib/debug.cpp:383 #7 debug_DisplayError at ../../../source/lib/debug.cpp:474 #8 debug_OnAssertionFailure at ../../../source/lib/debug.cpp:563 #9 topology::MaxLogicalPerCore at ../../../source/lib/sysdep/arch/x86_x64/topology.cpp:105 #10 topology::InitCpuTopology at ../../../source/lib/sysdep/arch/x86_x64/topology.cpp:158 #11 ModuleInit at ../../../source/lib/module_init.cpp:46 #12 topology::NumPackages at ../../../source/lib/sysdep/arch/x86_x64/topology.cpp:246 #13 RunHardwareDetection at ../../../source/ps/GameSetup/HWDetect.cpp:305 Potential duplicate: bug 1217865
Created attachment 1204272 [details] File: backtrace
Created attachment 1204273 [details] File: cgroup
Created attachment 1204275 [details] File: core_backtrace
Created attachment 1204276 [details] File: dso_list
Created attachment 1204277 [details] File: environ
Created attachment 1204278 [details] File: exploitable
Created attachment 1204279 [details] File: limits
Created attachment 1204280 [details] File: maps
Created attachment 1204281 [details] File: mountinfo
Created attachment 1204282 [details] File: namespaces
Created attachment 1204283 [details] File: open_fds
Created attachment 1204284 [details] File: proc_pid_status
Created attachment 1204285 [details] File: var_log_messages
This looks like memory corruption. I don't think we can do much about this. Looks like it happens only on F24 and only on i686. If you are constantly able to reproduce this bug, please report it to upstream.