infoForLog: and others (?) produce invalid data

Open jorgenpt opened this issue 14 years ago • 1 comments

There was an occurrence where an infoForLog: message was created as {ms: "foo"}, {ts: 1} - or maybe the {ts: 1} was a different message. This needs to be looked into - it could be a problem with the DMNullTracker.

Jul 27 '11 15:07 jorgenpt

This is probably caused by DMTracker (somehow) having a nil session - causing -[DMTracker infoWithType:] to return a nil dict (by passing nil as the first arg to "dictionaryWithObjectsAndKeys").

Apr 01 '12 22:04 jorgenpt