Debriefing > Questions, Help, & How To's

-debug mode

(1/1)

tsmith:
How do I enable it? The error message says to add it to my ./srcds_run command, but I've tried running it with the following and neither works:

MALLOC_CHECK_=0 ./srcds_run -debug -game /home/smitty/goldeneye/gesource/ +maxplayers 30 +map ge_dam

as well as

MALLOC_CHECK_=0 ./srcds_run -game /home/smitty/goldeneye/gesource/ +maxplayers 30 +map ge_dam -debug

And neither works. -- the terminal still says I should enable -debug to get the log file, and there is no debug.log in the folder I am running it in, my home folder, or in my gesource folder.

Running on ubuntu 14.04

*edit* I've also gone directly into srcds_run and modified the initial value of DEBUG from "" to 1, and it still seems to ignore it.

Thanks,

Smitty

killermonkey:
need output of:    ldd server_i486.so

within the gesource/bin/ directory

tsmith:
linux-gate.so.1 =>  (0xb771f000)
   libz.so.1 => /usr/lib32/libz.so.1 (0xb62d5000)
   libdl.so.2 => /lib32/libdl.so.2 (0xb62d0000)
   librt.so.1 => /lib32/librt.so.1 (0xb62c7000)
   libutil.so.1 => /lib32/libutil.so.1 (0xb62c3000)
   libnsl.so.1 => /lib32/libnsl.so.1 (0xb62aa000)
   steam_api_i486.so => not found
   tier0_i486.so => not found
   vstdlib_i486.so => not found
   libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xb61c1000)
   libm.so.6 => /lib32/libm.so.6 (0xb617b000)
   libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xb615e000)
   libc.so.6 => /lib32/libc.so.6 (0xb5fb2000)
   /lib/ld-linux.so.2 (0xb7720000)
   libpthread.so.0 => /lib32/libpthread.so.0 (0xb5f96000)


Thanks for the help!

cfultz:
Not attempting to hijack the thread but I'm having the same issue on Ubuntu. When I attempt to run the server, I receive the following (not sure if OP is experiencing this too or not):


--- Code: ---
Console initialized.
Segmentation fault
cat: hlds.2243.pid: No such file or directory
email debug.log to linux@valvesoftware.com
Mon Sep 26 23:56:37 EDT 2016: Server restart in 10 seconds
Mon Sep 26 23:56:40 EDT 2016: Server Quit

--- End code ---

Everything else OP has above is identical to my installation (except my server is on 16.04). Tried it as well on 14.04 with the exact same problems. Both servers are 64-bit.

EDIT: Found this thread as well but the resolution of deleting and reinstalling the entire server doesn't seem to work for me (fourth reinstall).

killermonkey:
Not enough information to determine a cause

Navigation

[0] Message Index