New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on the latest ReHLDS #1
Comments
v1.2b did work ~6-8 months ago with the then current versions of rehlds and regamecs_dll. |
@WPMGPRoSToTeMa, I just tested the lastest version (1.2 beta 2) and it really crashes my server.
Server info:
|
cuz Lines 380 to 387 in 83fc271
|
Fixes #1 by updating the memory pattern for `gMsgBuffer` and `gMsgType` variables.
Please check if #4 fixes the crash, here are the binaries: https://github.com/WPMGPRoSToTeMa/SafeNameAndChat/actions/runs/1801278702#artifacts.
Looks like an addition to the ReHLDS API would be the best option, but I may want to re-consider the current implementation. At this point I think it's better to keep the status quo. |
@WPMGPRoSToTeMa Now it works!
|
@WPMGPRoSToTeMa Don't you think that resolving for a symbol through elf symtab is more reliable than patterns?
This requires a consensus on adding this to the API, how safe is it to provide these globals variables in the 3rd party etc, |
Just tried Beta 2 on debian 12(testing/bookworm) with 5.15.0-3-amd64 #1 SMP Debian 5.15.15-2 (2022-01-30) x86_64 GNU/Linux, latest rehlds, regamedll and still crashes |
@Nord1cWarr1or, @DeNeDe thanks for the testing of this one!
Of course, thanks for the idea. At first I didn't understand what you meant, but now I see it. This is yet to be implemented, so I'll plan to add it for the final 1.2. Let's keep the pattern easy fix for the 1.2 Beta 3.
Yep, I'm also not happy about adding everything to the API, especially something very specific like this one. |
Fixes #1 by updating the memory pattern for `gMsgBuffer` and `gMsgType` variables.
This is fixed in 1.2 Beta 3 release. |
thank you for fixing. |
source: https://dev-cs.ru/threads/6927/page-3#post-118710
The text was updated successfully, but these errors were encountered: