It seems that logging get easily corrupted (at least with latest macOS 10.13.3). I think just reloading the logging kext is sufficient to only see crap anymore.
For a short workaround: how can the unified logging "system" be reset? (Other than restarting the entire OS?)
Thanks,
Hagen.
Thanks again,
yep you were right. I don't know why I didn't see them.
Unfortunately restarting either/both of the demons does not reset the logging system in a way so it cures the garbled output...
BTW. Its not only garbled, it seems also that the logging system accesses the log string at the wrong memory position. Here it seems that it reads the format string at a position skipping the string start which contained %s (to display the denoted string parameter)...
<decode: mismatch for [%x] got [STRING sz:59]>] {I am bit clueless right now, since logging is a very valueable and neccesary way of developing/debuggin kernel code. Often its not even possible/manageable to connect a debugger...
What can I do to progress here?
Thanks & cheers,
Hagen
What can I do to progress here?
I don’t have any workarounds, beyond those I’ve already discussed and don’t really work for your setup. My recommendation is that you open a DTS tech support incident and ask our kernel specialist about this.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"