Gordon: I probably should not answer since I have not looked at the logging in detail, but the console itself does not protect against a task getting preempted. Thus, at times, the output to the console gets all jumbled up.
Hope I am answering your question :-) > On Feb 26, 2016, at 3:58 PM, Gordon Chaffee <[email protected]> wrote: > > I ran into an issue with log messages and the nlip protocol when > communicating between newtmgr and a sim target. If a log message occurs > after the request is made but before the response is written, it causes the > stream to get out of sync, and newtmgr is unable to parse the response > since it expects a json response. > > In my case, I ran into it while adding a 'logs append <msg>' command to > test the logging facility, so the log message is written to the console and > interrupts the nlip stream 100% of the time. Outside of the specific case > I've run into, I think a context switch to another task that writes a log > message could interrupt any message exchange. > > Is my thinking correct about the potential problems of log messages being > written to console? > > Thanks, > Gordon
