Jump to content
  • 0

[zero] core dumped after stopping mangosd


kupix

Question

system: CentOS 6.4

kernel: 2.6.32-358.14.1.el6.centos.plus.x86_64

memory: 2GB

procesor: i7, two cores

this is what i get whet i'm stopping mangosd process (Ctrl + c) and with server shutdown 1 command:

22:37:28 Halting process...
*** glibc detected *** ./mangosd: free(): invalid pointer: 0x0000000004570cb8 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a8f4760e6]
/usr/lib64/libstdc++.so.6(_ZNSsD1Ev+0x39)[0x3a9d49d4c9]
/opt/mangoszero/lib/libmangosscript.so(_ZN6ScriptD1Ev+0x18)[0x7f8bed347242]
/opt/mangoszero/lib/libmangosscript.so(FreeScriptLibrary+0x6e)[0x7f8bed345ddf]
./mangosd(_ZN9ScriptMgr19UnloadScriptLibraryEv+0x3a)[0xad60e4]
./mangosd(_ZN9ScriptMgrD1Ev+0x1b)[0xacde75]
./mangosd(_ZN6MaNGOS11OperatorNewI9ScriptMgrE7DestroyEPS1_+0x1e)[0x8fcac1]
./mangosd(_ZN6MaNGOS9SingletonI9ScriptMgrNS_14SingleThreadedIS1_EENS_11OperatorNewIS1_EENS_14ObjectLifeTimeIS1_EEE16DestroySingletonEv+0x13)[0x8fa9ff]
/lib64/libc.so.6(exit+0xe2)[0x3a8f435da2]
/lib64/libc.so.6(__libc_start_main+0x104)[0x3a8f41ece4]
./mangosd[0x85a139]
======= Memory map: ========
00400000-00f65000 r-xp 00000000 fd:00 787461               /opt/mangoszero/bin/mangosd
01164000-0116b000 rw-p 00b64000 fd:00 787461               /opt/mangoszero/bin/mangosd
0116b000-01175000 rw-p 00000000 00:00 0 
01bd6000-076ce000 rw-p 00000000 00:00 0                 [heap]
3a8ec00000-3a8ec20000 r-xp 00000000 fd:00 404676             /lib64/ld-2.12.so
3a8ee1f000-3a8ee20000 r--p 0001f000 fd:00 404676             /lib64/ld-2.12.so
3a8ee20000-3a8ee21000 rw-p 00020000 fd:00 404676             /lib64/ld-2.12.so
3a8ee21000-3a8ee22000 rw-p 00000000 00:00 0 
3a8f000000-3a8f002000 r-xp 00000000 fd:00 404682             /lib64/libdl-2.12.so
3a8f002000-3a8f202000 ---p 00002000 fd:00 404682             /lib64/libdl-2.12.so
3a8f202000-3a8f203000 r--p 00002000 fd:00 404682             /lib64/libdl-2.12.so
3a8f203000-3a8f204000 rw-p 00003000 fd:00 404682             /lib64/libdl-2.12.so
3a8f400000-3a8f58a000 r-xp 00000000 fd:00 404677             /lib64/libc-2.12.so
3a8f58a000-3a8f789000 ---p 0018a000 fd:00 404677             /lib64/libc-2.12.so
3a8f789000-3a8f78d000 r--p 00189000 fd:00 404677             /lib64/libc-2.12.so
3a8f78d000-3a8f78e000 rw-p 0018d000 fd:00 404677             /lib64/libc-2.12.so
3a8f78e000-3a8f793000 rw-p 00000000 00:00 0 
3a8f800000-3a8f817000 r-xp 00000000 fd:00 404679             /lib64/libpthread-2.12.so
3a8f817000-3a8fa17000 ---p 00017000 fd:00 404679             /lib64/libpthread-2.12.so
3a8fa17000-3a8fa18000 r--p 00017000 fd:00 404679             /lib64/libpthread-2.12.so
3a8fa18000-3a8fa19000 rw-p 00018000 fd:00 404679             /lib64/libpthread-2.12.so
3a8fa19000-3a8fa1d000 rw-p 00000000 00:00 0 
3a8fc00000-3a8fc83000 r-xp 00000000 fd:00 404683             /lib64/libm-2.12.so
3a8fc83000-3a8fe82000 ---p 00083000 fd:00 404683             /lib64/libm-2.12.so
3a8fe82000-3a8fe83000 r--p 00082000 fd:00 404683             /lib64/libm-2.12.so
3a8fe83000-3a8fe84000 rw-p 00083000 fd:00 404683             /lib64/libm-2.12.so
3a90400000-3a90407000 r-xp 00000000 fd:00 404680             /lib64/librt-2.12.so
3a90407000-3a90606000 ---p 00007000 fd:00 404680             /lib64/librt-2.12.so
3a90606000-3a90607000 r--p 00006000 fd:00 404680             /lib64/librt-2.12.so
3a90607000-3a90608000 rw-p 00007000 fd:00 404680             /lib64/librt-2.12.so
3a90800000-3a9081d000 r-xp 00000000 fd:00 404697             /lib64/libselinux.so.1
3a9081d000-3a90a1c000 ---p 0001d000 fd:00 404697             /lib64/libselinux.so.1
3a90a1c000-3a90a1d000 r--p 0001c000 fd:00 404697             /lib64/libselinux.so.1
3a90a1d000-3a90a1e000 rw-p 0001d000 fd:00 404697             /lib64/libselinux.so.1
3a90a1e000-3a90a1f000 rw-p 00000000 00:00 0 
3a90c00000-3a90c15000 r-xp 00000000 fd:00 404690             /lib64/libz.so.1.2.3
3a90c15000-3a90e14000 ---p 00015000 fd:00 404690             /lib64/libz.so.1.2.3
3a90e14000-3a90e15000 r--p 00014000 fd:00 404690             /lib64/libz.so.1.2.3
3a90e15000-3a90e16000 rw-p 00015000 fd:00 404690             /lib64/libz.so.1.2.3
3a91400000-3a91416000 r-xp 00000000 fd:00 404696             /lib64/libresolv-2.12.so
3a91416000-3a91616000 ---p 00016000 fd:00 404696             /lib64/libresolv-2.12.so
3a91616000-3a91617000 r--p 00016000 fd:00 404696             /lib64/libresolv-2.12.so
3a91617000-3a91618000 rw-p 00017000 fd:00 404696             /lib64/libresolv-2.12.so
3a91618000-3a9161a000 rw-p 00000000 00:00 0 
3a9a400000-3a9a45d000 r-xp 00000000 fd:00 404704             /lib64/libfreebl3.so
3a9a45d000-3a9a65c000 ---p 0005d000 fd:00 404704             /lib64/libfreebl3.so
3a9a65c000-3a9a65d000 r--p 0005c000 fd:00 404704             /lib64/libfreebl3.so
3a9a65d000-3a9a65e000 rw-p 0005d000 fd:00 404704             /lib64/libfreebl3.so
3a9a65e000-3a9a662000 rw-p 00000000 00:00 0 
3a9a800000-3a9a974000 r-xp 00000000 fd:00 283011             /usr/lib64/libcrypto.so.1.0.0
3a9a974000-3a9ab73000 ---p 00174000 fd:00 283011             /usr/lib64/libcrypto.so.1.0.0
3a9ab73000-3a9ab8c000 r--p 00173000 fd:00 283011             /usr/lib64/libcrypto.so.1.0.0
3a9ab8c000-3a9ab96000 rw-p 0018c000 fd:00 283011             /usr/lib64/libcrypto.so.1.0.0
3a9ab96000-3a9ab9a000 rw-p 00000000 00:00 0 
3a9ac00000-3a9ac07000 r-xp 00000000 fd:00 404705             /lib64/libcrypt-2.12.so
3a9ac07000-3a9ae07000 ---p 00007000 fd:00 404705             /lib64/libcrypt-2.12.so
3a9ae07000-3a9ae08000 r--p 00007000 fd:00 404705             /lib64/libcrypt-2.12.so
3a9ae08000-3a9ae09000 rw-p 00008000 fd:00 404705             /lib64/libcrypt-2.12.so
3a9ae09000-3a9ae37000 rw-p 00000000 00:00 0 
3a9b400000-3a9b403000 r-xp 00000000 fd:00 404714             /lib64/libcom_err.so.2.1
3a9b403000-3a9b602000 ---p 00003000 fd:00 404714             /lib64/libcom_err.so.2.1
3a9b602000-3a9b603000 r--p 00002000 fd:00 404714             /lib64/libcom_err.so.2.1
3a9b603000-3a9b604000 rw-p 00003000 fd:00 404714             /lib64/libcom_err.so.2.1
3a9bc00000-3a9bc16000 r-xp 00000000 fd:00 404684             /lib64/libgcc_s-4.4.7-20120601.so.1
3a9bc16000-3a9be15000 ---p 00016000 fd:00 404684             /lib64/libgcc_s-4.4.7-20120601.so.1
3a9be15000-3a9be16000 rw-p 00015000 fd:00 404684             /lib64/libgcc_s-4.4.7-20120601.so.1
3a9d000000-3a9d002000 r-xp 00000000 fd:00 394243             /lib64/libkeyutils.so.1.3
3a9d002000-3a9d201000 ---p 00002000 fd:00 394243             /lib64/libkeyutils.so.1.3
3a9d201000-3a9d202000 r--p 00001000 fd:00 394243             /lib64/libkeyutils.so.1.3
3a9d202000-3a9d203000 rw-p 00002000 fd:00 394243             /lib64/libkeyutils.so.1.3
3a9d400000-3a9d4e8000 r-xp 00000000 fd:00 271953             /usr/lib64/libstdc++.so.6.0.13
3a9d4e8000-3a9d6e8000 ---p 000e8000 fd:00 271953             /usr/lib64/libstdc++.so.6.0.13Przerwane (core dumped)

any ideas?

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

First off, I always treat my server as if it was a live server for Blizzard. I use

.server shutdown 30 0

I don't know if that second number helps any, but in windows, you have to make sure that the exit code is a 0 or windows freaks out and tries to debug the program. At least on my computer. ;)

Now, as for the actual error log...

It looks like your debugger is trying to track back to the library files that are being reference at the time of the crash. As for the invalid pointer, I have gotten similar errors when I am trying to actually start mangosd. Once, there was a bad push on the repo and when I ran mangosd it would give me an error about a missing dll which actually did compile but was not being properly referenced. ;)

Unless your server is actually breaking (since you are shutting down) and not saving stuff to the database or something else weird is occurring, I personally would not worry about it until

Ugh! I want to help you more, so badly, but I am unable to. I was never able to get MaNGOS to compile even under *NIX. Sorry.

Link to comment
Share on other sites

I never thought about asking about that even. That could very well be the issue at hand. None of your log looked very consequential to me. Try recompiling with Release mode. And if that doesn't work, try 32-bit release. I know you have a 64-bit os, but perhaps something was overlooked in the source code...?

I have to use Visual Studio Express, so I can't compile 64-bit and as such have no clue if that could be part of the issue or not. Sorry. ???

Link to comment
Share on other sites

This might be fixed "by itself" when going through what coverity scan has to say about zero. Does this always happen or just at times? And does it only happen when using the shutdown command? Also, do you close it from the console window or via chat in wow? (don't remember if that's possible, but it's worth asking)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use