6 Replies
      Latest reply on Feb 13, 2019 1:42 AM by eskimo
      hagen Level 1 Level 1 (0 points)

        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?)




        • Re: unified logging corrupted
          hagen Level 1 Level 1 (0 points)

          Issue persists up to today. Bug has been reported.


          To recap:

          The output of a kext using the unified logging via console or terminal is garbled after kextloading a rebuilt kext if another version was loaded before (macOS 10.12/10.13).


          Steps to Reproduce:

          build a kext with logging. kextload. rebuild it with slightly changed source. kextunload/kextload.


          Anyone cares?

          • Re: unified logging corrupted
            eskimo Apple Staff Apple Staff (10,585 points)

            Anyone cares?

            I, for one, care.  Alas, I don’t have any obvious suggestions for how to move forward here.  My recommendation is that you open a DTS tech support incident and I, or one of my colleagues, can take a proper look at this.

            Share and Enjoy

            Quinn “The Eskimo!”
            Apple Developer Relations, Developer Technical Support, Core OS/Hardware
            let myEmail = "eskimo" + "1" + "@apple.com"