Numbered Steps to Reproduce Problem:
1. compile code below
2. run code below
3. observe DD crashing
Code Snippet (if applicable) to Reproduce Problem:
/datum/proc/global/foo() // this can be 'global', 'static' or 'const'
world.log << "foo!"
/world/New()
var/datum/D = new /datum
D.foo()
Expected Results: Compilation failure with a descriptive error.
Actual Results: Compilation 'success', DD crashes on execution.
Does the problem occur:
Every time? Or how often? Every time
In other games? N/A
In other user accounts? Unknown
On other computers? Unknown
When does the problem NOT occur? Unknown
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? Happens as described in 509.1319 and 510.1337.
Workarounds: None.
Trace:
DM:
DM compiler version 510.1337
loading static_proc.dme
static_proc.dme:6:warning: D: variable defined but not used
saving static_proc.dmb
static_proc.dmb - 0 errors, 1 warning (4/9/16 7:07 pm)
DD:
Sat Apr 9 19:07:54 2016
Auto-safety mode: ultrasafe (no file access)
World opened on network port 5000.
Welcome BYOND! (5.0 Beta Version 510.1337)
BUG: Crashing due to an illegal operation!
proc name: New (/world/New)
usr: null
src: world
call stack:
world: New()
Backtrace for BYOND 510.1337 on Linux:
Generated at Sat Apr 9 19:07:54 2016
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb24]
libbyond.so [0xf7238000, 0x0], 0x234893
linux-gate.so.1 [0xf7775000, 0xf7775bd0], [0xf7775000, 0xf7775bd0]
libbyond.so [0xf7238000, 0x0], 0x234893
libbyond.so [0xf7238000, 0x0], 0x25546e
libbyond.so [0xf7238000, 0x0], 0x25dc83
libbyond.so [0xf7238000, 0x0], 0x25efab
libbyond.so [0xf7238000, 0x0], 0x214a96
libbyond.so [0xf7238000, 0x0], 0x21697f
libbyond.so [0xf7238000, 0x0], 0x212ac9
libbyond.so [0xf7238000, 0x0], 0x213463
libbyond.so 0x2807f0, 0x280837
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ad84]
libc.so.6 0x18430, 0x18527 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a731]
Recent proc calls:
/world/New
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