Have you been trying to create a file like:
- ~/.local/lib/python3.6/site-packages/file.pth
with a non ASCII character, like òàè, and run the debugger plugin? Just to verify whether the issue happens only in my system.
In my system the locale command produces:
LANG=it_IT.UTF-8 LANGUAGE=it_IT LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" LC_TIME="it_IT.UTF-8" LC_COLLATE="it_IT.UTF-8" LC_MONETARY="it_IT.UTF-8" LC_MESSAGES="it_IT.UTF-8" LC_PAPER="it_IT.UTF-8" LC_NAME="it_IT.UTF-8" LC_ADDRESS="it_IT.UTF-8" LC_TELEPHONE="it_IT.UTF-8" LC_MEASUREMENT="it_IT.UTF-8" LC_IDENTIFICATION="it_IT.UTF-8" LC_ALL=
It seems ok.
I use a python sub-system with different locations for the modules and for this reason I use the .pth file. I use a great deal of python programs but I never experienced problems with it before using the debugger plugin.
I verified that gdb works if I run it from the terminal on the same file and putting some non ASCII character in the .pth file, therefore the problem is not in the gdb itself.
I don't have experience in geany code but I ask myself why would the debugger plugin use python code. Maybe because it is predisposed to support python debugging? Massimo massimo