Log for http://crashes.uberent.com/report/index/f2594fbc-a452-4548-8d9b-691b22150826 attached. Flags were: PA --coherent-log-level=TRACE --gl-debug Some mods where enabled (some map packs, hotbuild2, better system view, pastats, who deleted that)
Another crash in libc-2.21.so@0x349c8 INFO build version 87296, id 2015090987296 The log: (PA --coherent-log-level=DEBUG --gl-debug) http://s000.tinyupload.com/index.php?file_id=96538934501735063448 The crash automated report: http://crashes.uberent.com/report/index/c22fc990-0a9d-472f-9e8c-e278b2150918
Hmm, 0x349c8@libc is probably an address to something generic like _libc_sigabort or _raise. :-( You could, just for fun, try to install the debug symbols for your libc (How to do this depends on your distribution. Google would be a good start). But I'm not sure if Ubers crash report tool supports external symbols.
@ crizmess EDIT: Coming from Debian and using Fedora now, I got confused, the glibc-devel package is not what I need here. For my own reference here is the command line for Fedora 22: Code: $ su -c 'dnf debuginfo-install glibc-2.21-7.fc22.x86_64' ../.. Installed : glibc-debuginfo.x86_64 2.21-7.fc22 glibc-debuginfo-common.x86_64 2.21-7.fc22 We'll see how it helps. Thank you!
