• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

TFS 1.X+ tfs 1.3 8.60 Segmentation fault

Lbtg

Intermediate OT User
Joined
Nov 22, 2008
Messages
2,306
Reaction score
129
Hello today server crashed and there is very strange error saved....

Can anyone gimme hints please what is this or what can cause this, any info will be helpfull please



C++:
Core was generated by `./tfs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000055e9df6ff2ec in ?? ()
[Current thread is 1 (LWP 24084)]
(gdb) bt full
#0  0x000055e9df6ff2ec in ?? ()
No symbol table info available.
#1  0x00007fbfc2ca94e0 in ?? ()
No symbol table info available.
#2  0x0000000000000018 in ?? ()
No symbol table info available.
#3  0x00007fbfc2ca9400 in ?? ()
No symbol table info available.
#4  0x000055e9df6fe62c in ?? ()
No symbol table info available.
#5  0x0000000000000010 in ?? ()
No symbol table info available.
#6  0x0000000000000018 in ?? ()
No symbol table info available.
#7  0x00007fbfc2ca9420 in ?? ()
No symbol table info available.
#8  0x000055e9df6fdb6e in ?? ()
No symbol table info available.
#9  0x00007fbfc6096040 in ?? ()
No symbol table info available.
#10 0x0000000000000018 in ?? ()
No symbol table info available.
#11 0x00007fbfc2ca9440 in ?? ()
--Type <RET> for more, q to quit, c to continue without paging--
 
To elaborate further on what Nekiro wrote:
The executable file is currently running without "debug symbols"; which works as a documentation of the functions executed inside the binary executable file.
So without debug symbols, we can't see which part of the source code that crashed the server.

Here is a guide on how to compile a binary file that contains debug symbols:

If you run this file through gdb and it crashes, bt full will show us more concrete information where the segmentation fault happened.
 
Your bt full says absolutely nothing, compile with debug symbols and get the bt full again
To elaborate further on what Nekiro wrote:
The executable file is currently running without "debug symbols"; which works as a documentation of the functions executed inside the binary executable file.
So without debug symbols, we can't see which part of the source code that crashed the server.

Here is a guide on how to compile a binary file that contains debug symbols:

If you run this file through gdb and it crashes, bt full will show us more concrete information where the segmentation fault happened.
This crash was like 1 of 10, last 9 crashes everything was fine, what i mean with fine, that there was a normal readable errorors in code.

Anyway it seems your ansfers have helped.


Shall we know something else about this matter ? :)
 
Back
Top