GNU bug report logs - #33548
25.1; GUD GDB doesn't decode file paths correctly

Previous Next

Full log

Message #8 received at 33548 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: ksqsf <i <at> ksqsf.moe>
Cc: 33548 <at> debbugs.gnu.org
Subject: Re: bug#33548: 25.1; GUD GDB doesn't decode file paths correctly
Date: Thu, 29 Nov 2018 21:35:53 +0200

> From: ksqsf <i <at> ksqsf.moe>
> Date: Fri, 30 Nov 2018 00:58:34 +0800
> Feedback-ID: bizesmtp:ksqsf.moe:qybgforeign:qybgforeign2
> 
> It seems that GDB MI doesn't decode file paths correctly, which can
> result in some really weird unexpected behaviors.
> 
> For example, it attempts to find file
> /home/ksqsf/我的坚果云/"/home/ksqsf/\346\210\221\347\232\204\345\235\232\346
> \236\234\344\272\221/code.cpp"
> 
> I traced down to the source and found that gdb-get-source-file, gdb-
> get-source-file-list, and gdb-get-location don't decode file paths
> using a correct coding system. (In my case, UTF-8.) Instead, they
> simply use 'read'.

Does it help to set gdb-mi-decode-strings to utf-8?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.