[linux] segfaults with build 258 and nvidia 310.19 drivers
eyeris
Join Date: 2013-09-10 Member: 188088Members
Looks like build 258 is incompatible with the nvidia 310.19 drivers on linux. The game worked (for a substandard but better definition of worked) with these drivers as of build 256 and 257. Plenty of segfaults in other libs too though.
[397360.121404] ns2_linux32[25131]: segfault at 0 ip 00000000f37b7500 sp 00000000d3a2afb8 error 4 in libc-2.17.so[f367d000+1a9000] [849853.097429] ns2_linux32[17197]: segfault at 0 ip 00000000f19b0a46 sp 00000000ffb405e0 error 4 in libnvidia-glcore.so.310.19[f0576000+1cb1000] [1203111.189557] ns2_linux32[2238]: segfault at 0 ip 00000000f1a05a46 sp 00000000ffe56c90 error 4 in libnvidia-glcore.so.310.19[f05cb000+1cb1000] [1205002.565482] ns2_linux32[2970]: segfault at 0 ip 00000000f1963a46 sp 00000000ffb4c820 error 4 in libnvidia-glcore.so.310.19[f0529000+1cb1000] [1292888.812705] ns2_linux32[6906]: segfault at 0 ip 00000000f19aba46 sp 00000000ffee28e0 error 4 in libnvidia-glcore.so.310.19[f0571000+1cb1000] [1293107.439296] ns2_linux32[7880]: segfault at 0 ip 00000000f1a43a46 sp 00000000ffbc3710 error 4 in libnvidia-glcore.so.310.19[f0609000+1cb1000] [1550415.480694] ns2_linux32[21194]: segfault at 0 ip 00000000f3819500 sp 00000000d31fcfb8 error 4 in libc-2.17.so[f36df000+1a9000] [1556538.101440] ns2_linux32[21708]: segfault at 0 ip 00000000f3786500 sp 00000000d9c1dfb8 error 4 in libc-2.17.so[f364c000+1a9000] [1561338.287818] ns2_linux32[24273]: segfault at 0 ip 00000000f1a31a46 sp 00000000ff97d850 error 4 in libnvidia-glcore.so.310.19[f05f7000+1cb1000] [1632959.100005] ns2_linux32[29183]: segfault at 0 ip 00000000f3769500 sp 00000000cf14cfb8 error 4 in libc-2.17.so[f362f000+1a9000] [1703709.666316] ns2_linux32[1693]: segfault at 0 ip 00000000f19e9a46 sp 00000000fff80020 error 4 in libnvidia-glcore.so.310.19[f05af000+1cb1000] [2107108.632693] ns2_linux32[18642]: segfault at 25fd9 ip 00000000f6c65229 sp 00000000ff920200 error 4 in libSpark_Core.so[f6a37000+6c0000] [2392257.053188] ns2_linux32[3384]: segfault at 0 ip 00000000f3775500 sp 00000000cf157fb8 error 4 in libc-2.17.so[f363b000+1a9000] [2400127.302314] ns2_linux32[3777]: segfault at 0 ip 00000000f377f500 sp 00000000ce944fb8 error 4 in libc-2.17.so[f3645000+1a9000] [2799407.220132] ns2_linux32[22371]: segfault at 0 ip 00000000f1989a46 sp 00000000ff9a24a0 error 4 in libnvidia-glcore.so.310.19[f054f000+1cb1000] [3011356.123094] ns2_linux32[2751]: segfault at 0 ip 00000000f19b5a46 sp 00000000ffe14e70 error 4 in libnvidia-glcore.so.310.19[f057b000+1cb1000] [3011574.044282] ns2_linux32[2904]: segfault at 0 ip 00000000f19dba46 sp 00000000ffa376f0 error 4 in libnvidia-glcore.so.310.19[f05a1000+1cb1000] [3186542.946600] ns2_linux32[13060]: segfault at 0 ip 00000000f1969a46 sp 00000000ffd18f60 error 4 in libnvidia-glcore.so.310.19[f052f000+1cb1000] [3186858.838389] ns2_linux32[13250]: segfault at 0 ip 00000000f194aa46 sp 00000000ff9ebba0 error 4 in libnvidia-glcore.so.310.19[f0510000+1cb1000]
Comments
As for reproduction steps: just play the game. I have noticed that it happens more often after entering gorge tunnels, evolving higher lifeforms, and buying weapons from the armory.
Anything special about the armory and the evolution that you can think of for me to try out? does ti crash opening a menu? or buying? etc etc
After my game crashed, log.txt was old -- from my previous match. I also have a full backtrace with all local context and a core dump (1.9 GB, 495 MB compressed) that I'd be willing to send to the devs, given an email address. I don't feel comfortable posting those here since they possibly contain my NS2 credentials and possibly a steam auth token.
Did you do anything with gorge tunnels when the crash happend?
This isn't exactly the same bug but they both relate to the shotgun, as do a few other crash posts recently:
http://forums.unknownworlds.com/discussion/132992/linux-crash-while-being-shot-by-shotgun-by-entrace-to-energy-flow
I can't tell based on comparing what the bug reporting system we use is saying and the last patch's changelog..
(changelog does not mention it but reporting system says the fix made it in)
Do you still get this from entering gorge tunnels?
If so please provide a new BT.
Thanks