Crash in UpdateClientData(edict_s const*, int, clientdata_s*) () from /home/server3367/game/cstrike/dlls/cs.so #957
Comments
|
You need to attach crashdump |
|
Hosting does not provide access to the dump file. Such errors (the ReHLDS+ReGame combination) began to appear regularly after updating ReGame to 5.26. The crash happens at a completely random time. |
s1lentq
added a commit
that referenced
this issue
Aug 6, 2024
jonathan-up
added a commit
to jonathan-up/ReGameDLL_CS
that referenced
this issue
Aug 11, 2024
* Update workflows/build.yml Fix temporarily testdemos * Fix compiler warnings * Fixed a bug in spectator move with no apply friction when stopped * Update build.yml * Add support IN_RUN key for +speed button in spectator/noclip and walk moves Add cheat impulse for enable Noclip with air accelerate * try fix a crash due to the deletion of an item in an unusual way related rehlds#870, rehlds#752, rehlds#924, rehlds#957 * Extend KickBack functionalities (rehlds#980) --------- Co-authored-by: s1lentq <s1lentsk@yandex.ru> Co-authored-by: Francisco Muñoz <fjmunozpena@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `./hlds_linux -game cstrike +ip 62.122.213.230 +port 27015 +map de_dust2 +maxpla'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000 in ?? ()
#0 0x00000000 in ?? ()
#1 0xb2a7f28b in UpdateClientData(edict_s const*, int, clientdata_s*) () from /home/server3367/game/cstrike/dlls/cs.so
#2 0xb1394494 in ?? ()
#3 0x00000005 in ?? ()
#4 0xb68a39a5 in SV_WriteClientdataToMessage () from /home/server3367/game/engine_i486.so
#5 0x0000019b in ?? ()
#6 0x0000019b in ?? ()
#7 0x00000016 in ?? ()
#8 0x00000001 in ?? ()
#9 0x00000000 in ?? ()
ReGameDLL version: 5.26.0.668-dev
Build date: 19:02:48 Dec 31 2023
Build from: d3c0ec8
ReHLDS version: 3.13.0.788-dev
Build date: 12:57:18 Jul 24 2023 (3390)
Build from: rehlds/rehlds@f955b07
The text was updated successfully, but these errors were encountered: