[XAT]

My server is encountering strange and annoying crashes few times everyday, so i decided to install debugging binaries, i compiled them on my machine and then put it on server.
But when it crashes gdb shows everytime same trace but i cant realy know what is the crash reason.

Reading symbols from hlds_i686...done.
[New Thread 10599]
[New Thread 10600]
[New Thread 3386]
[New Thread 3375]

Reading symbols from cstrike/addons/metamod/dlls/metamod_i386.so...done.
Loaded symbols for cstrike/addons/metamod/dlls/metamod_i386.so
Reading symbols from cstrike/dlls/cs_i386.so...done.
Loaded symbols for cstrike/dlls/cs_i386.so
Reading symbols from cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/sqlite_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/sqlite_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/fun_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/fun_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/engine_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/engine_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/fakemeta_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/fakemeta_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/geoip_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/geoip_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/nvault_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/nvault_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/cstrike_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/cstrike_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/csx_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/csx_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/hamsandwich_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/hamsandwich_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/sockets_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/sockets_amxx_i386.so
Reading symbols from cstrike/addons/amxmodx/modules/regex_amxx_i386.so...done.
Loaded symbols for cstrike/addons/amxmodx/modules/regex_amxx_i386.so

(gdb) bt
#0  0xf56b6026 in CBasePlayer::TraceAttack(entvars_s *, float, Vector, TraceResult *, int) () from cstrike/dlls/cs_i386.so
#1  0xff8bc6dc in ?? ()
#2  0xbeb85a1c in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) print TraceResult
$1 = {void (<anonymous struct> * const)} 0xf5409cd8 <TraceResult>
(gdb) info symbol 0xf5409cd8
TraceResult::TraceResult() in section .text of cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
(gdb) print traceresult
$2 = {cell (AMX *, cell *)} 0xf511633b <traceresult>
(gdb) info symbol 0xf511633b
traceresult(tagAMX*, int*) in section .text of cstrike/addons/amxmodx/modules/engine_amxx_i386.so

(gdb) print (char*)cmd_args
$3 = 0xf79e0b6b "9"
(gdb) info symbol 0xf79e0b6b
string.367 + 11 in section .bss of engine_i686.so

I've got all amxx ( 1.8.2-dev ) binaries debugged so, just one simple question, does this backtrace mean this is not amxx fault ?
Well there is frame about TraceAttack, but what caused it to crash, is TraceAttack there by mistake ?

Please help.

PS. If this is a wrong section, please move my thread, thanks.

[fysiks]

Remove all non-default AMX Mod X plugins and see if it still happens. If it doesn't then you know it's not the fault of AMX Mod X default plugins/modules.

[XAT]

Originally Posted by fysiks Remove all non-default AMX Mod X plugins and see if it still happens. If it doesn't then you know it's not the fault of AMX Mod X default plugins/modules.

This is not very helpfull answear, i'm am giving you detailed info about crash and it is obvious that this won't happend with amxx standard plugins becouse everyone would spam thread like this, don't you think ?

What i mean is if i have all amx symbols library debugged and loaded and i still dont have full backtrace does this mean not amxx problem ?

[Exolent[jNr]]

Find which plugin is causing the crash.
Then, we can look at the code to see what it's trying to do.

[XAT]

If i would know what plugin crashes i coud fix it by myself

(gdb) source analyze/analyze.gdb
Available commands (AmxModX-related):
    amx_analyze:       Analyze the dump and try to figure out which AmxModX plugin caused it
    amx_listplugins:   List all loaded AmxModX plugins
    amx_listplayers:   List all players as seen by AmxModX
Available commands (metamod-related):
    meta_analyze:      Analyze the dump and try to figure out which metamod plugin caused it
Available commands (generic):
    cmd_args:          Dump the cmd string

If you have no idea where to start, just type '*_analyze' and let it figure out for you
(gdb) amx_analyze
No symbol "amx" in current context.

Once again, if gdb has loaded all symbols from debug binaries and it still dosen't show any proper backtrace can the crash reason still be caused by amxx ?

[Exolent[jNr]]

You could see if it was a specific plugin by disabling all non-standard AMXX plugins.

If it doesn't crash, then start enabling them 1 by 1 until it crashes.
Whatever the last enabled plugin was would be the cause.

[wickedd]

Delete

[XAT]

Well i have many plugins and i could do what you say but this crash comes randomly when there are players on my server.
I can't test it without plugins becouse there will not be players what assumes no crash.

I tested my debugged binaries with cousing some controlled crash with get_pdata_int with invalid parameters and it gives excellent backtrace, but what about this ?
How can in interpret this backtrace.

[fysiks]

YOu should be able to survive disabling one plugin at a time and let it run for a few days. Disable the plugins that were most recently added. Then disable small ones or ones that add admin functions first.

This is the most reliable method (in this community).

I know it's not what you want to hear but that is how we would do it if it was our server.

[XAT]

Wew... but disabling about 60plugins and leaving each for few days and see it crashing would take me months x.x.

Maybe this is hl engine bug becouse backtrace points directly to cs_i386 ?
I'm using 5006 Binary with antiautobuybug and antidlfile.