Sorry, the VisualGDB semihosting console only supports UTF-8 as it has become a de-facto standard encoding for all non-Latin characters. Would switching the encoding of your source files to UTF-8 be a reasonable workaround?
No, we can’t change encoding of sources, because CP866 is used to communicate with third-party device. All messages in this device should be stored exactly in CP866.
We already have workaround – print short message in debug console (using latin characters), and then print actual data. So we can see, that data transferred. Anyway, thank you for your answer.
Thanks for explaining this – it makes sense. Good to know you have found the workaround. Let us know if you run into further problems and we will be happy to help.