If liblog is used in interrupt context or by some kernels threads => libc isn't neither thread safe (newlib implementation i.e. the most common libc for MCU:s) nor re-entrant. Latter is true not only MCU use-cases.
printf with friends are also known to be unnecessarily big. For most logging purposes, floating-point handling and ditto formatting is quite un-necessary.
This may not be a liblog issue but a system issue (link which library). There may however be a need to distinguish one API from another in base both need to be used.
Labelled "investigate" for the causes mentioned above.
If liblog is used in interrupt context or by some kernels threads => libc isn't neither thread safe (newlib implementation i.e. the most common libc for MCU:s) nor re-entrant. Latter is true not only MCU use-cases.
printf with friends are also known to be unnecessarily big. For most logging purposes, floating-point handling and ditto formatting is quite un-necessary.
This may not be a liblog issue but a system issue (link which library). There may however be a need to distinguish one API from another in base both need to be used.
Labelled "investigate" for the causes mentioned above.