Dream Daemon misreporting errors?

ID:1994816
 
Dec 8 2015, 12:04 am (Edited on Dec 8 2015, 12:11 am)
BYOND Version:509.1315
Operating System:Windows 7 Home Premium 64-bit
Web Browser:Chrome 47.0.2526.73
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:
Dream Seeker and Dream Daemon appear to be inconsistent in outputting a runtime error. Namely, Dream Seeker reports the correct error, while Dream Daemon reports an error with an entirely unrelated, previously functioning piece of code.

Numbered Steps to Reproduce Problem:
I tried to write a simpler test case for this, but I couldn't reproduce it there. Instead, I've packaged the source code that I initially received the strange error in.

Code Snippet (if applicable) to Reproduce Problem:

// My simple test case.
mob/Login()
    ..()
    var obj/o = new (src)
    del o
    o.name = "test"


Expected Results:
Dream Seeker reports, as intended:

runtime error: Cannot modify null.name.
proc name: Login (/player/Login)
  source file: main.dm,41
  usr: (src)
  src: LordAndrew (/player)
  src.loc: the tileset (1,1,1) (/tileset)
  call stack:
LordAndrew (/player): Login()

Actual Results:
Dream Daemon reports...?:

runtime error: invalid object type 14:0
proc name: TakeDamage (/mob/proc/TakeDamage)
  source file: main.dm,124
  usr: LordAndrew (/player)
  src: world
  usr.loc: the tileset (1,1,1) (/tileset)
  call stack:
world: TakeDamage(Cannot modify null.name. (/exception))
LordAndrew (/player): Login()

When does the problem NOT occur?
When ran through Dream Seeker, the runtime error is reported correctly.

Dec 8 2015, 12:06 am
In the context of the linked demo, I commented out TakeDamage() to see what would happen. Dream Daemon moved on to reporting another error with a piece of code that previously had no issues:

runtime error: Cannot read null.pixel_x
proc name: ShakeScreen (/mob/verb/ShakeScreen)
  source file: main.dm,134
  usr: LordAndrew (/player)
  src: world
  usr.loc: the tileset (1,1,1) (/tileset)
  call stack:
world: ShakeScreen(Cannot modify null.name. (/exception))
LordAndrew (/player): Login()

Something is definitely not right here.
Dec 8 2015, 1:13 am
I'll take a look tomorrow and see what's up.
Dec 8 2015, 12:47 pm
Lummox JR changed status to 'Unverified'
Dec 8 2015, 12:49 pm
I can't get this to happen, whether I join remotely or locally. Dream Seeker and Dream Daemon both report the error message correctly for me.
Dec 8 2015, 6:04 pm
runtime error: invalid object type 14:0

runtime error: Cannot read null.pixel_x


I mentioned this in the BYOND Skype thread, but both of these are related to the new client variables added. Maybe your server is trying to run an old version of BYOND? When I run my project in old versions I get these two errors from animating client.color and client.pixel_x/y
Dec 8 2015, 6:28 pm
In response to Rushnut
I've double-checked and as far as I can tell, I'm not having any version conflicts. The pager, Dream Maker, and Dream Daemon all report that they're on version 509.1315.
Dec 8 2015, 7:50 pm
The invalid object message you're seeing comes from animate().