logger: handle 'char' type in messages

Fixes errors like:
ERROR [logger] No definition for topic char[10] key;uint8_t[2] _padding0; found
when the Debug logging profile is selected.
This commit is contained in:
Beat Küng 2019-07-03 10:46:14 +02:00 committed by Daniel Agar
parent 7ab48dae57
commit c92c90d4d9
No known key found for this signature in database
GPG Key ID: FD3CBA98017A69DE

View File

@ -1798,7 +1798,8 @@ void Logger::write_format(LogType type, const orb_metadata &meta, WrittenFormats
strcmp(type_name, "uint64_t") != 0 &&
strcmp(type_name, "float") != 0 &&
strcmp(type_name, "double") != 0 &&
strcmp(type_name, "bool") != 0) {
strcmp(type_name, "bool") != 0 &&
strcmp(type_name, "char") != 0) {
// find orb meta for type
const orb_metadata *const*topics = orb_get_topics();