I need help debugging this error, if anyone can help that would be great.
DreamDaemon --version BYOND 5.0 Beta (Version 502.1219) on Linux
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ac08]
libbyond.so 0x3955d0, 0x395b69
[0xb7748000, 0xb774840c], [0xb7748000, 0xb774840c]
libbyond.so 0x3955d0, 0x395b69
libbyond.so 0x3867b0, 0x38693c
libbyond.so 0x387110, 0x387162
libbyond.so 0x2e1ef0, 0x2e203e
libbyond.so 0x245490, 0x245690
libbyond.so 0x2468c0, 0x246be3
libbyond.so 0x24c4c0, 0x24c4d9
libbyond.so [0xb71fa000, 0x0], 0x25ad72
libbyond.so 0x25b920, 0x25ba3f
libbyond.so [0xb71fa000, 0x0], 0x297a89
libbyond.so 0x298f80, 0x2991f1
libbyond.so [0xb71fa000, 0x0], 0x29a10a
libbyond.so [0xb71fa000, 0x0], 0x2a6180
libbyond.so 0x2b6860, 0x2b697e
libbyond.so 0x2bde90, 0x2bdf43
libbyond.so [0xb71fa000, 0x0], 0x2beb15
libbyond.so [0xb71fa000, 0x0], 0x2a7d6c
libbyond.so 0x2b6860, 0x2b697e
libbyond.so 0x2bde90, 0x2bdf43
libbyond.so [0xb71fa000, 0x0], 0x2be918
libbyond.so [0xb71fa000, 0x0], 0x2a7d6c
libbyond.so 0x2b6860, 0x2b697e
libbyond.so 0x2bde90, 0x2bdf43
libbyond.so [0xb71fa000, 0x0], 0x2be918
libbyond.so [0xb71fa000, 0x0], 0x2a7d6c
libbyond.so 0x2b6860, 0x2b697e
libbyond.so 0x2bde90, 0x2bdf43
libbyond.so [0xb71fa000, 0x0], 0x2be918
libbyond.so [0xb71fa000, 0x0], 0x2a7d6c
libbyond.so 0x2b6860, 0x2b697e
libbyond.so 0x2bde90, 0x2bdf43
libbyond.so [0xb71fa000, 0x0], 0x2be918
libbyond.so [0xb71fa000, 0x0], 0x2a7d6c
libbyond.so [0xb71fa000, 0x0], 0x2b675c
libbyond.so 0x2b7ba0, 0x2b7ca5
libbyond.so [0xb71fa000, 0x0], 0x27d944
libbyond.so 0x34e520, 0x34e6bc
libbyond.so 0x31dd20, 0x31df29
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a69c]
libc.so.6 0x193e0, 0x194d3 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a0e1]
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
ID:1445874
 Dec 15 2013, 6:02 pm
|
|||||||||||||
Resolved
| |||||||||||||
Please try this in the latest 503.1222. When it crashes, it should provide some new info about the DM procs in use. Also, you may want to try disabling the map-threads if that turns out to be causing new crashes.
You can compile your game in pre-500 versions if you want to ensure that old clients can login. | |
Stephen001 resolved issue with message:
If this issue still persists, please post here, and I'll re-open the issue. | |
Mon Dec 23 21:16:16 2013
World opened on network port 2110.
Welcome BYOND! (5.0 Public Version 500.1213)
BUG: Crashing due to an illegal operation!
Backtrace for BYOND 500.1213 on Linux:
Generated at Mon Dec 23 21:16:24 2013
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ab18]
libbyond.so 0x3905f0, 0x390b89
libc.so.6 [0xb756f000, 0x0], 0x2ada0
libbyond.so 0x3905f0, 0x390b89
libbyond.so 0x3817d0, 0x38195c
libbyond.so 0x382130, 0x382182
libbyond.so 0x2dd6e0, 0x2dd7cd
libbyond.so 0x2425a0, 0x2425f4
libbyond.so 0x27d530, 0x27e195
libbyond.so 0x27b4b0, 0x27b629
libbyond.so 0x27b930, 0x27baef
libbyond.so 0x2d0ca0, 0x2d0ce3
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a52b]
libc.so.6 0x16be0, 0x16cc6 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x8049ff1]
This seemingly came out of the blue.