Server Crash (gdb)

[Scura]

Hey guys,

I am trying to reup an old server just for develop some little stuff for a friend (based on Reza 1776).

During the process I've encountered tons of strange errors (like some strange lib missing, tons of errors with db and so on, that i didn't meet on any installation before...). I managed how to fix all of that, and fortunately after 4 days of 24/7 work I am pretty near to have set-up everything!

 

After have started the server I meet an "invalid version" error which forced me to bypass this check for correctly run the client... but this solution didn't fix all my problems...

/monthly_2021_11/invalid.png.0fd30cb51e3e9841d5f48820a681d083.png" />

I managed how to fix the invalid version error, however the GameServer directly crash on char selection without any further explanation of that? . I've also tried to debug it with gdb, but the debugger show me that some libraries are missing (when in reality everything is correctly setup and installed ... ???)



(this is the gdb output)

 

I never met that error before ... someone have an idea about how to fix that?

 

[Scura]

I would like update that post with more details:

I've found another similar error while trying to run the helper now. That's error too seems to be linked at the boost library, for the installation process of boost I used the following commands:

yum update
yum install epel-release

yum install boost boost-thread boost-devel

Screenshot of the Helper error:

2

May be the issue related at boost at this point? 

[Scura]

Fixed (db correupted)

 

#Closed

[Scura]

I want to share the solution i followed, maybe it may be useful for someone:

 

1) First install gdb:

yum -y update
yum install gdb

2) Attach the debug at any source file like:

gdb ./Helper
gdb ./SubHelper
gdb ./GameServer_d
...
...
...

3) When the program crash, gdb should pop up the console an allow you to type command (you can understand it because the program is ofc crashed and the console should write (gdb) with an empity line where write commands.

At this point, type "backtrace" for backtrace the bug. Gdb should show you the stack of the crashed program and the reason why it crashed!

4) Go ahead with your fix!

 

Note: in some cases gdb may need external dependencies for debug the program, in this case it should tell you which ones you need to install!

 

#Close

[merl0@]

On 11/3/2021 at 3:26 PM, Scura said:




I want to share the solution i followed, maybe it may be useful for someone:



 



1) First install gdb:




yum -y update
yum install gdb


2) Attach the debug at any source file like:




gdb ./Helper
gdb ./SubHelper
gdb ./GameServer_d
...
...
...


3) When the program crash, gdb should pop up the console an allow you to type command (you can understand it because the program is ofc crashed and the console should write (gdb) with an empity line where write commands.




At this point, type "backtrace" for backtrace the bug. Gdb should show you the stack of the crashed program and the reason why it crashed!


4) Go ahead with your fix!



 



Note: in some cases gdb may need external dependencies for debug the program, in this case it should tell you which ones you need to install!



 



#Close




ty useful