Native sim test output wraps lines at 256 chars #96773
              
                Unanswered
              
          
                  
                    
                      bryceschober
                    
                  
                
                  asked this question in
                General
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
The Zephyr unit test output gets forced to wrap at 256 characters, and that is getting in the way of some custom printing that I'm doing on test assertion failure, as in:
FWIW, I ran the executable under the debugger, and I was able to trace execution down into
cbvprintf_package()inlib/os/cbprintf_packaged.c, with a fully intact string of about 1800 characters, but then the path of execution got confusing, and I gave up.How would I find where this force line-wrapping output behavior is implemented, and how might I adjust it?
Originally posted by @bryceschober in #96173
Beta Was this translation helpful? Give feedback.
All reactions