Skip to content
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

Segmentation fault on client error #49

Open
CheezusChrust opened this issue May 14, 2024 · 0 comments
Open

Segmentation fault on client error #49

CheezusChrust opened this issue May 14, 2024 · 0 comments
Assignees
Labels

Comments

@CheezusChrust
Copy link

CheezusChrust commented May 14, 2024

Just started getting this recently. The first time a client receives an error with this module loaded, the server immediately segfaults.

Segmentation fault (core dumped)
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem

I know nothing about debugging but here's the initial output from gdb as per the guide here. I'm not sure how to get more valuable info from it.

Reading symbols from srcds_linux...
(No debugging symbols found in srcds_linux)
BFD: warning: /home/avtomat/serverfiles/core has a segment extending past end of file
[New LWP 3026220]
[New LWP 3027235]
[New LWP 3027234]
[New LWP 3027224]
[New LWP 3026223]
[New LWP 3026222]
[New LWP 3027222]
[New LWP 3026224]
[New LWP 3027226]
[New LWP 3027220]
[New LWP 3027236]
[New LWP 3026246]
--Type <RET> for more, q to quit, c to continue without paging--
[New LWP 3027229]
[New LWP 3027227]
[New LWP 3026247]
[New LWP 3026249]
[New LWP 3027230]
[New LWP 3026248]
[New LWP 3027219]
[New LWP 3026744]

warning: Error reading shared library list entry at 0x64646436
Cannot access memory at address 0x61353069
Cannot access memory at address 0x61353065
Failed to read a valid object file image from memory.
Core was generated by `./srcds_linux -game garrysmod -ip 0.0.0.0 -port 27016 +host_workshop_collection'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf041b72e in ?? ()
[Current thread is 1 (LWP 3026220)]

No debug.log was generated.

@danielga danielga self-assigned this May 15, 2024
@danielga danielga added the bug label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants