Linux trying to exit - Error 11

[Gangrenous]

Getting thousands of these, around these lines.

Code: Select all

	//let the stream factory know were done with this stream
	if(eqs){
		eqs->Close();
		try{
			eqs->ReleaseFromUse();
		}
		catch(...){}
	}
	eqs = NULL;

Here is the gdb dump

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffedffb700 (LWP 17164)]
Mutex::lock (this=0x7ffff2491448) at ../common/Mutex.cpp:53
53              if (name.length() > 0){
(gdb) bt
#0  Mutex::lock (this=0x7ffff2491448) at ../common/Mutex.cpp:53
#1  0x000000000050e70e in ReleaseFromUse (this=0x7ffff248f400)
    at ../common/../WorldServer/../common/EQStream.h:284
#2  Client::~Client (this=0x7ffff23aa3d0, __in_chrg=<optimized out>) at client.cpp:193
#3  0x000000000053cfe5 in Delete (key=0x7ffff23aa3d0)
    at ../common/../WorldServer/MutexHelper.h:101
#4  HandleDeletes<Client*>::CheckDeletes (this=this@entry=0x7ffff0846368,
    force=force@entry=false) at ../common/../WorldServer/MutexHelper.h:184
#5  0x000000000053d240 in MutexList<Client*>::update (this=0x7ffff08462a8, force=false)
    at ../common/../WorldServer/MutexList.h:261
#6  0x0000000000712257 in size (include_pending=true, this=0x7ffff08462a8)
    at MutexList.h:132
#7  ZoneServer::ClientProcess (this=this@entry=0x7ffff0846090) at zoneserver.cpp:2596
#8  0x000000000071c51c in ZoneServer::Process (this=this@entry=0x7ffff0846090)
    at zoneserver.cpp:1205
#9  0x000000000071ca21 in ZoneLoop (tmp=0x7ffff0846090) at zoneserver.cpp:5587
#10 0x00007ffff6897b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00007ffff65e195d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x0000000000000000 in ?? ()

[Gangrenous]

Another one tonight.

Code: Select all

#0  0x00007ffff6538165 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff653b3e0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ffff657239b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007ffff657bbe6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007ffff658098c in free () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x000000000072166c in deallocate (__p=<optimized out>, this=<optimized out>)
    at /usr/include/c++/4.7/ext/new_allocator.h:100
#6  _M_put_node (__p=<optimized out>, this=<optimized out>)
    at /usr/include/c++/4.7/bits/stl_list.h:339
#7  std::_List_base<unsigned int, std::allocator<unsigned int> >::_M_clear (
    this=this@entry=0x7ffff16db9c0) at /usr/include/c++/4.7/bits/list.tcc:80
#8  0x000000000072499c in ~_List_base (this=0x7ffff16db9c0, __in_chrg=<optimized out>)
    at /usr/include/c++/4.7/bits/stl_list.h:379
#9  ~list (this=0x7ffff16db9c0, __in_chrg=<optimized out>)
    at /usr/include/c++/4.7/bits/stl_list.h:436
#10 MutexList<unsigned int>::~MutexList (this=0x7ffff16db940, __in_chrg=<optimized out>)
    at MutexList.h:55
#11 0x0000000000733b85 in Delete (key=0x7ffff16db940) at MutexHelper.h:101
#12 DeleteValue (this=<optimized out>) at MutexHelper.h:123
#13 MutexMap<unsigned int, MutexList<unsigned int>*>::update (this=this@entry=0x143658a0,
    force=force@entry=false) at MutexMap.h:276
#14 0x0000000000734191 in MutexMap<unsigned int, MutexList<unsigned int>*>::clear (
    this=0x143658a0, delete_all=<optimized out>) at MutexMap.h:132
#15 0x000000000071c33d in ZoneServer::Process (this=this@entry=0x14364030)
    at zoneserver.cpp:1166
#16 0x000000000071ca21 in ZoneLoop (tmp=0x14364030) at zoneserver.cpp:5587
#17 0x00007ffff6897b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#18 0x00007ffff65e195d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#19 0x0000000000000000 in ?? ()

[Jabantiz]

Sig 11 is a tricky one as it usually refers to corrupted memory, however the call stacks tell you were the corrupted memory was encountered but not where it got corrupted so they are hard to chase down. Does this only happen when you close the server, and if so how do you close the server?

[Gangrenous]

The first one was just out of the blue, not doing anything that I remember. The second one was during a repop.

Closing the server, I guess I am just lazy and normally do a CTR-C to close it. If there is a better way I am definitely open to doing it right.

[Gangrenous]

I figured out some of my issues but a new one popped up. This is absolutely database related but I have no idea how it could be. I am forced third person and cannot zoom out. It is the strangest thing. If I use a blank database, it never happens.

[Gangrenous]

I think most all my issues have been database issues. What I have noticed from my prior experience at EqEmu is some aspects of the database design allowed you to move zones and spawns, etc in bulk. I could move certain zone aspects between databases with issues, other things you could not. The automatic PK incrementing could get in the way. I could already see an issue here when moving my Antonica work from one database to the other. Being able to move zones around are huge to me. If I get a zone completely done I want to be able to archive it as a single SQL and no matter what work has been done, place it back into a different database. Looking at the design here most of that can be done, but not all. What I have been doing is reordering the table keys for things like location, placement to match the zone id's. I have that work done and now the emu is not crashing on repops nor am I stuck in 3rd person on occasion. So I think the entire issue was constraint issues not being adhered to on all tables.

[Jabantiz]

Sorry I wasn't more help on this one, I almost never use Linux so I just suck when it comes to debugging issues on it.

[Gangrenous]

I did find out more. It actually was not stored in the database anywhere, the third person issue. It finally did it on a bare install. It seemed to relate to when I have to close the server out with a CTRL-C and then having to kill the process with the kill command. After that, I have to do in the client and delete the cache folder to make my character go back into normal view.

Yep, strange.

[WarnerSkese]

Hey Daemon, any update on this issue? I'm running into the same error on Ubuntu 14.04. I've had a myriad of other errors, but this is the most recent.