Update 1.50->1.55 = instant crash - Page 2

Sp4rt4n · 08-26-2005 , 22:24

i believe its only for linux, because my windows server is running fine with mysql

(dunno if you knew that or not already)

juKay · 08-27-2005 , 04:55

Quote:

Originally Posted by BAILOPAN

juKay: is that a debug compiled version? If not, can you build one or have me build one for you?

also what mysql version is the module (4.0 or 4.1)

Please build one for me, I don't have the latest source set up on any box yet. Dunno if it's 4.0 or 4.1, it's the default mysql file from the linux tar file. md5sum is 27e4bd19f951ddef3d74ba7c8ff3eb83, mySQL server is 4.0.

juKay · 08-27-2005 , 05:31

I got some time over so I updated from CVS and made a debug version of the mysql module, make debug. Btw why is the mysql folder not in the dlls folder, like sqlite, mssql and pgsql?

My GCC version is 3.3.4 do I need to upgrade to 3.4 to get valid debug output for you?

Anyway I ran the server with gdb again but this time I only get this line when it crashes:

0x00000000 in ?? ()

Can you tell me how to run gdb to get more output? As it is right now I only do:

gdb ./hlds_i686
set args -autoupdate -game cstrike -maxplayers 17 +map de_dust2
run

BAILOPAN · 08-30-2005 , 02:52

Please try the newer MySQL module from http://forums.alliedmods.net/showthr...=147130#152202.

If it doesn't stop the crashing, use "make debug" to build a debug version of the binary (it will be large!), then you can post it here.

juKay · 08-30-2005 , 10:19

That version did not solve the problem. From what I can see it still gives me the same error. Only sql-plugin running on the server is admin_sql.amxx.

Debug from your version:

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209820960 (LWP 5580)]
0xb7ea1703 in strlen () from /lib/tls/libc.so.6

#0  0xb7ea1703 in strlen () from /lib/tls/libc.so.6
#1  0xb4413f4e in CMysqlResultSet::CMysqlResultSet () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#2  0x081308c8 in ?? ()
#3  0x00000001 in ?? ()
#4  0x081309a8 in ?? ()
#5  0xb444d8d8 in ?? () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#6  0x081309a8 in ?? ()
#7  0x081393d8 in ?? ()
#8  0x081308c0 in ?? ()
#9  0xb4413439 in CMysqlDatabase::Query () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#10 0x081393d8 in ?? ()
#11 0x081308c0 in ?? ()
#12 0xbf8a52d4 in ?? ()
#13 0xb444dc08 in vtable for CMysqlDatabase () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#14 0x081308c0 in ?? ()
#15 0xb4529730 in g_Mysql () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#16 0xb444d8d8 in ?? () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#17 0x081308c0 in ?? ()
#18 0xb4443346 in ?? () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#19 0xb452804c in g_fn_GetAmxStringLen () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#20 0xb44148bf in IResultSet::~IResultSet () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#21 0x081308c0 in ?? ()
#22 0xb4443346 in ?? () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#23 0xb45a5f80 in _lc_Fmt_ () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#24 0xbf8a52e4 in ?? ()
#25 0xb459d300 in TeamIds::TeamEle::uid () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#26 0x00000000 in ?? ()
#27 0x00000037 in ?? ()
#28 0xbf8a5350 in ?? ()
#29 0x0810e868 in ?? ()
#30 0xb4414810 in IResultSet::~IResultSet () from cstrike/addons/amxmodx/modules/mysql_amxx_i386.so
#31 0xbf8a5314 in ?? ()
#32 0xb457ea67 in amx_Callback () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
Previous frame inner to this frame (corrupt stack?)

With a debug build of the mysql module (included below)

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210349344 (LWP 5589)]
0xb7e20703 in strlen () from /lib/tls/libc.so.6

#0  0xb7e20703 in strlen () from /lib/tls/libc.so.6
#1  0xb4396b44 in CMysqlResultSet (this=0x81309a8, pResult=0x81393d8, pDb=0x81308c0) at CMysqlResultSet.cpp:16
#2  0xb4395db4 in CMysqlDatabase::Query (this=0x81308c0, fmt=0xb43c2ad4 "%s") at CMysqlDatabase.cpp:64
#3  0xb439748b in sql_query (amx=0x810e870, params=0x81518dc) at mysql_amxx.cpp:81
#4  0xb44fda67 in amx_Callback () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#5  0xb45043dc in amx_exec_jit () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#6  0xbf825fc8 in ?? ()
#7  0x0813f6b6 in ?? ()
#8  0xb450429a in amx_exec_jit () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#9  0x0810e870 in ?? ()
#10 0x0813c5cc in ?? ()
#11 0x00000000 in ?? ()
#12 0x0001040c in ?? ()
#13 0x00000000 in ?? ()
#14 0xb45104d8 in ?? () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
#15 0xbf826088 in ?? ()
#16 0x00010ad8 in ?? ()
#17 0xbf826040 in ?? ()
#18 0xb44fea1e in amx_Exec () from /cs_server_cs1/cstrike/addons/amxmodx/dlls/amxmodx_mm_i386.so
Previous frame inner to this frame (corrupt stack?)

BAILOPAN · 08-30-2005 , 11:38

Would it be possible for you to give me SSH access to debug this? I have an idea of the problem but I need to get into the debugger personally, to step through this in disassembly.

juKay · 08-30-2005 , 12:27

Information sent as PM

BAILOPAN · 08-30-2005 , 13:44

Thank you very much! When tracking down this error on your server, I realized it was an old problem: there is a bug in MySQL where mysql_fetch_fields returns garbage. theqizmo notified me of this a long time ago but I figured it would never come up.

However, apparently your server is one that displays this odd bug. I've added two things: a fix to use a different MySQL call which is not buggy, and prevention from this sort of needless crash.

Thanks again for letting me debug on your server! Locking report.