unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ksqsf <i@ksqsf.moe>
Cc: 33548@debbugs.gnu.org
Subject: bug#33548: 25.1; GUD GDB doesn't decode file paths correctly
Date: Thu, 29 Nov 2018 21:35:53 +0200	[thread overview]
Message-ID: <83tvjzd6cm.fsf@gnu.org> (raw)
In-Reply-To: <1543510714.13628.2.camel@ksqsf.moe>+4500C08A0B612909 (message from ksqsf on Fri, 30 Nov 2018 00:58:34 +0800)

> From: ksqsf <i@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?





       reply	other threads:[~2018-11-29 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1543510714.13628.2.camel@ksqsf.moe>
2018-11-29 19:35 ` Eli Zaretskii [this message]
2018-11-30  2:03   ` bug#33548: 25.1; GUD GDB doesn't decode file paths correctly ksqsf
     [not found]   ` <1543543399.17576.1.camel@ksqsf.moe>
2018-11-30  7:39     ` Eli Zaretskii
2018-11-30  8:03       ` ksqsf
     [not found]       ` <1543565036.30749.1.camel@ksqsf.moe>
2018-11-30  8:47         ` Eli Zaretskii
2018-11-29 16:58 ksqsf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83tvjzd6cm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33548@debbugs.gnu.org \
    --cc=i@ksqsf.moe \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).