3
« on: July 24, 2013, 07:42:12 am »
I tend to use my mud as a glorified chat client, and mostly to toy around with stuff as it peaks my interest. I took the plunge again a couple weeks back and got DS3.7a up with FluffOS 2.27, and it was stable. Since I am pretty much stock DS, when a upgrade comes out I tend to just drop the lib in and restart the driver. Did so again yesterday when I saw DS3.8 was out. Have had a couple crashes since. Here is the stacktrace:
...
Running autoexec, please wait...
Autoexec daemon run complete. (52ms)
******** FATAL ERROR: couldn't find object PW? in obj_table
FluffOS driver attempting to exit gracefully.
(current object was /secure/sefun/sefun)
--- trace ---
Object: /secure/daemon/instances, Program: /secure/daemon/instances.c
in heart_beat() at /secure/daemon/instances.c:677
Object: /secure/daemon/instances, Program: /secure/daemon/instances.c
in CheckConnections() at /secure/daemon/instances.c:637
Object: /secure/sefun/sefun, Program: /secure/sefun/sefun.c
in socket_names() at /secure/sefun/sockets.c:25
' CATCH' in '/secure/sefun/sefun.c' ('/ secure/sefun/sefun') /secure/sefun/sockets.c:25
--- end trace ---
*** glibc detected *** /home/skout/Servers/DS/Obscurum/bin/driver: malloc(): smallbin double linked list corrupted: 0x00000000028ab570 ***
I thought to look for any changes in instances.c, sefun.c & socket.c from 3.6-> 3.8 via a github repo which tracks DS, but no changes that I could tell. All that was happening was me idling, mud-client (tintin++) and mud are on the same box. Am I just hitting some new idle timeout? Should I regress back to an earlier approved version of fluffos or vault into the 3.0 tags?
Thanks,
Scott