[gdb] Python output encoded incorrectly with non-ASCII

[AnyOldName3]

Description / Steps to reproduce the issue

• gdb
• Within GDB, run python print("\u00a7"). It prints §.
• Exit GDB with exit, then run python -c 'print("\u00a7")'. It prints §.

Expected behavior

Both tests should print §.

Actual behavior

Within GDB, it prints §. Outside of GDB, it prints §.

Verification

• I have verified that my MSYS2 is up-to-date before submitting the report (see https://www.msys2.org/docs/updating/)

Windows Version

MINGW64_NT-10.0-19045

MINGW environments affected

• MINGW64
• MINGW32
• UCRT64
• CLANG64
• CLANGARM64

Are you willing to submit a PR?

I failed to find the root cause as it's none of the obvious suspects, so a PR from me is unlikely.

[AnyOldName3]

To be on the safe side, I checked this in WSL2 with the same terminal emulator, and it works fine there, so it's definitely an MSYS2 problem.

[oltolm]

You need to set chcp 65001. If you use bash, add this to .bashrc

$WIN_ROOT/System32/chcp.com 65001 > /dev/null

[AnyOldName3]

That's at best a workaround. It's not a listed requirement of MSYS2 that the system's code page is UTF-8 (UTF-8 doesn't even work fully until Windows 10 1903, which is above the listed minimum supported Windows version for MSYS2), and plenty of other MSYS2-packaged applications behave just fine. It's also not a workaround I can use, as I maintain software that needs to work on machines using a classic fixed-width eight bit code page, and need to be able to test that there aren't any encoding bugs on such machines, so need those bugs to be reproducible on my machine, too.

I actually don't need a workaround at all, as I already have one for the situation that led me to discover this problem.