Logging with char array

RE: Logging with char array

corbin — Thu, 07 Jul 2022 21:56:59 GMT

This does work, thank you.

RE: Logging with char array

ovrebekk — Thu, 30 Jun 2022 12:13:14 GMT

What if you do it like this instead?

NRF_LOG_INFO("%s", s);

Then I believe the string will be copied internally, and you don't have to worry about the original memory being overwritten.

Best regards
Torbjørn

RE: Logging with char array

corbin — Wed, 29 Jun 2022 21:26:15 GMT

Okay, my teammate just found this little nugget in here:

"Since the logs are not processed directly, it is risky to pass pointers as arguments, especially to variables that do not have static addresses, for example variables allocated on the stack. By the time the log is processed, the pointer can point to invalid data. The logger provides a mechanism to overcome this issue by enforcing a string that is copied into the internal logger buffer."

With the suggestion to use `NRF_LOG_PUSH()`.

Thankfully, this solves the problem. I still don't understand why if we can see the data is not corrupted the original did not work though.