Trace Report (Server Crash)

ID:619247
 
Apr 2 2012, 12:55 pm
BYOND Version:493
Operating System:Linux
Web Browser:Chrome 18.0.1025.142
Applies to:Dream Daemon
Status: Unverified
Thus far we've been unable to verify or reproduce this bug. Or, it has been observed but it cannot be triggered with a reliable test case. You can help us out by editing your report or adding a comment with more information.
Descriptive Problem Summary:
This message and report came up in Putty after my Linux-hosted server crashed (due to a corrupt save file, or something). Your program asked me to post it, so I'm obliging the kind computer's request.

Numbered Steps to Reproduce Problem:
The server crashed when this file was accessed, but I can't tell you much more than that.

Here's the log:

World opened on network port 1280.
Welcome BYOND! (4.0 Public Version 493.1116)
The BYOND hub reports that port 1280 is reachable.
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 493.1116 on Linux:
Generated at Tue Apr 3 02:49:13 2012

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a708]
libbyond.so 0x21d2f0, 0x21d416
libc.so.6 [0xb773e000, 0x0], 0x28e20
libbyond.so 0x21d2f0, 0x21d416
libbyond.so [0xb7b9a000, 0x0], 0x208f8a
libbyond.so [0xb7b9a000, 0x0], 0x208003
libbyond.so [0xb7b9a000, 0x0], 0x2093be
libbyond.so [0xb7b9a000, 0x0], 0x207ef0
libbyond.so 0x2088c0, 0x20897b
libbyond.so [0xb7b9a000, 0x0], 0x2956c4
libbyond.so [0xb7b9a000, 0x0], 0x29874b
libbyond.so [0xb7b9a000, 0x0], 0x279021
libbyond.so 0x28f500, 0x28f610
libbyond.so 0x28f660, 0x28f715
libbyond.so 0x291880, 0x291938
libbyond.so [0xb7b9a000, 0x0], 0x2083a6
libbyond.so [0xb7b9a000, 0x0], 0x209089
libbyond.so [0xb7b9a000, 0x0], 0x208003
libbyond.so 0x2088c0, 0x20897b
libbyond.so [0xb7b9a000, 0x0], 0x2956c4
libbyond.so [0xb7b9a000, 0x0], 0x29874b
libbyond.so [0xb7b9a000, 0x0], 0x279021
libbyond.so 0x28f500, 0x28f610
libbyond.so 0x28f660, 0x28f715
libbyond.so [0xb7b9a000, 0x0], 0x290a29
libbyond.so [0xb7b9a000, 0x0], 0x27ca4f
libbyond.so 0x28f500, 0x28f610
libbyond.so 0x28f660, 0x28f715
libbyond.so 0x291880, 0x291938
libbyond.so [0xb7b9a000, 0x0], 0x2083a6
libbyond.so 0x2088c0, 0x208a24
libbyond.so [0xb7b9a000, 0x0], 0x28949f
libbyond.so 0x28f500, 0x28f610
libbyond.so [0xb7b9a000, 0x0], 0x28207d
libbyond.so [0xb7b9a000, 0x0], 0x28e0eb
libbyond.so 0x31bfe0, 0x31c13c
libbyond.so 0x2ef410, 0x2ef646
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a203]
libc.so.6 0x15db0, 0x15e8c (__libc_start_main)
DreamDaemon [0x8048000, 0x8049b9c], [0x8048000, 0x8049cd1]

To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1
Apr 2 2012, 2:06 pm
Curious. I can see this is happening when reading a list from a savefile, but the error doesn't make sense to me. It's saying that it can't fill in the newly created list with nulls, but that the memory has already been allocated successfully. I've seen issues like this in Linux traces before but I've never been able to diagnose the memory corruption that leads up to the problem (which I'm sure is the real issue).

If you have a copy of the savefile or can narrow down which one it is, that would be very helpful. For now I'll have to push this to Unverified because I don't have enough info to reproduce this.
Apr 2 2012, 2:06 pm
Lummox JR changed status to 'Unverified'