ID:66544
 
BYOND Version:439
Operating System:FreeBSD
Web Browser:
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.
Don't know what caused the crash.

BUG: Crashing due to an illegal operation!

Backtrace for BYOND 439.1015 on FreeBSD:
Generated at Sat Apr 25 10:58:41 2009

DreamDaemon [0x8048000, 0x80494ec], [0x8048000, 0x804ab8b]
libbyond.so 0x1f2f3c, 0x1f320d
libbyond.so 0x1f380c, 0x1f3ba6
libbyond.so 0x28d4f4, 0x28d53b
libbyond.so 0x265220, 0x265498
DreamDaemon [0x8048000, 0x80494ec], [0x8048000, 0x8049dd7]
DreamDaemon [0x8048000, 0x80494ec], [0x8048000, 0x8049ab6]

To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/developer/forum/?forum=2


DreamDaemon will now produce a file called 'core' that you can send to the
BYOND developers for more analysis. For instructions, please contact us at
http://www.byond.com/support/
For Lummox JR or Tom, this appears to occur at line 4884 of smsg.cpp. It seems to be accessing a pointer that must have been freed but was not set to null. Looking through the code, I have a hard time figuring out how that could even happen. The object type in question is only deleted in a couple of places, and they seem pretty safe from this perspective.

I'm setting this to 'Unverified' since the cause isn't determined, and I'm not sure if there's much else we can do unless it happens again.