gdb

our server still crash and crash all the time
so now i try this gdb thingy

did i correctly?

Code:

srcds2@R14573:~$ ps ux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
srcds2   21659  0.0  0.0  24812  1140 ?        Ss   06:05   0:01 SCREEN -A -m -d -S server2_2 ./src
srcds2   21660  0.0  0.0  10816  1768 pts/1    Ss+  06:05   0:00 /bin/sh ./srcds_run -game cstrike
srcds2   22971 37.9  2.3 363860 190068 pts/1   Rl+  16:40  40:00 ./srcds_linux -game cstrike -tos -
srcds2   23007  0.0  0.0  24944  1312 ?        Ss   16:48   0:00 SCREEN -S gdb
srcds2   23008  0.0  0.0  20748  3636 pts/6    Ss   16:48   0:00 /bin/bash
srcds2   23027  0.0  1.2 124684 103680 pts/6   S+   16:50   0:00 gdb attach 22971

and when a crash comes, where will the info stored?


first crash, and all i got is this????????

Code:

0xf4412a7a in CBaseEntity::GetRefEHandle ()
---Type <return> to continue, or q <return> to quit---continue
from /home/srcds2/orangebox/cstrike/bin/server.so
(gdb) return
Make selected stack frame return now? (y or n) y

#0  0xf7533b92 in CStaticPropMgr::IsStaticProp ()
from /home/srcds2/orangebox/bin/engine.so
(gdb) continue
Continuing.
[Thread 0xeae78b90 (LWP 22974) exited]
[New Thread 0xeae78b90 (LWP 23222)]

Program received signal SIGILL, Illegal instruction.
[Switching to Thread 0xf7ccdad0 (LWP 22971)]
0xe812ddf1 in ?? ()
(gdb) continue
Continuing.

Program received signal SIGHUP, Hangup.
[Switching to Thread 0xeae78b90 (LWP 23222)]
0xf7f17d80 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib32/libpthread.so.0
(gdb)

another ....

Code:

Continuing.
[Thread 0xeb078b90 (LWP 24272) exited]
[New Thread 0xeb078b90 (LWP 24317)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf7c8aad0 (LWP 24269)]
0x0d476a0c in ?? ()
(gdb)

btw you sweet
how should i know about this?

looks like run more stable with new rev

looks like server runs stable again .. o.O
even i did nothing

was up for 24 hours now
i was forced to restart because of "round draw" bug for too long uptime


confusing shit again

SRCDS behavior can indeed be very erratic, especially when it's stimulated properly. Maybe there was an incorrect offset which sourcemod updated when you restarted the server. Who knows.