• 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!

Segmentation Fault

leo123456

New Member
Joined
Jun 13, 2009
Messages
29
Reaction score
0
Hi people,

I use OTX 8.6, and my server crashed sometimes.

The error is this:

Segmentation Fault.

My config.lua with tile settings:

Lua:
protectionTileLimit = 0
houseTileLimit = 0
tileLimit = 0

Please, someone is crash my server with some bug.

Thanks.
 
You are probably using Linux.
Install gdb and run otx through gdb
once your server crash
write bt full
and you will get full console error,
just copy it and paste here on otland so we can resolve it.
 
sudo apt-get install gdb
once you fresh installed it
write
cd directory
gdb
file tfs
run
once you run it do ctrl+a+c and just write quit
Something like that, maybe you have to use screen -S directory to hold it open whole time but try like that
 
sudo apt-get install gdb
once you fresh installed it
write
cd directory
gdb
file tfs
run
once you run it do ctrl+a+c and just write quit
Something like that, maybe you have to use screen -S directory to hold it open whole time but try like that

I installed gbd with the command:
sudo apt-get install gdb
What should I do now?
My server is online in screen mode.
 
Hello leo123456,

did you compile the binary with the switch -g in the configuration?

If yes, please proceed to starting your server with following commands:
$ gdb *binaryname*
$ run

Once your server crashes type:
$ backtrace

That will lead you to more information regarding the crash, which you should post here so we can take a look and try to help you further.

Kindest Regards,
Okke
 
@Monkey Budex

Code:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff2d74700 (LWP 4646)]
0x0000000000585060 in std::__find<__gnu_cxx::__normal_iterator<Player* const*, std::vector<Player*, std::allocator<Player*> > >, Player const*> (
    __first=<error reading variable: Cannot access memory at address 0x0>,
    __last=__last@entry=, __val=@0x7ffff2d73a38: 0x1e5e800)
    at /usr/include/c++/4.8/bits/stl_algo.h:166
166               if (*__first == __val)
(gdb) bt
#0  0x0000000000585060 in std::__find<__gnu_cxx::__normal_iterator<Player* const*, std::vector<Player*, std::allocator<Player*> > >, Player const*> (
    __first=<error reading variable: Cannot access memory at address 0x0>,
    __last=__last@entry=, __val=@0x7ffff2d73a38: 0x1e5e800)
    at /usr/include/c++/4.8/bits/stl_algo.h:166
#1  0x0000000000583f89 in find<__gnu_cxx::__normal_iterator<Player* const*, std::vector<Player*> >, Player const*> (__val=@0x7ffff2d73a38: 0x1e5e800,
    __last=..., __first=...) at /usr/include/c++/4.8/bits/stl_algo.h:4441
#2  Party::isPlayerInvited (this=this@entry=0x12023480,
    player=player@entry=0x1e5e800, result=result@entry=false) at party.cpp:433
#3  0x0000000000583fbe in Party::removeInvite (this=0x12023480,
    player=player@entry=0x1e5e800) at party.cpp:173
#4  0x00000000005be49c in Player::clearPartyInvitations (
    this=this@entry=0x1e5e800) at player.cpp:5477
#5  0x00000000005c3539 in Player::onCreatureDisappear (this=0x1e5e800,
    creature=<optimized out>, isLogout=<optimized out>) at player.cpp:1649
#6  0x00000000004eef03 in Game::removeCreature (this=0x88bb40 <g_game>,
    creature=0x1e5e800, isLogout=isLogout@entry=true) at game.cpp:1022
#7  0x00000000004544e3 in ProtocolGame::logout (this=0x1223c1e0,
    displayEffect=<optimized out>, forceLogout=<optimized out>)
    at protocolgame.cpp:405
#8  0x000000000048b740 in operator() (this=0x812d4c40)
    at /usr/include/boost/function/function_template.hpp:767
---Type <return> to continue, or q <return> to quit---
 
Back
Top