From: "Dedeco Balaco Baco via gdb" <gdb@sourceware.org>
To: <gdb@sourceware.org>
Subject: How to debug with gdbtui and utf-8 source files?
Date: Wed, 18 Oct 2017 17:50:00 -0000 [thread overview]
Message-ID: <1311475292.483858.1508348766742@mail.yahoo.com> (raw)
In-Reply-To: <1311475292.483858.1508348766742.ref@mail.yahoo.com>
I have:
- a terminal set to UTF-8 in an OS where UTF-8 locales are installed: Mate Terminal 1.12.1 (does not matter, as long as its character encoding is utf-8)
- a C source file which contains (both) utf-8 comments and utf-8 strings
- gdbtui:
$ gdbtui --version
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
The program compiles and works flawlessly, with its output being correctly shown in the terminal.
gdbtui, on the other hand, does not show the comments correctly, making them hard to read and also braking the size and making a few lines occupy two screenlines. This makes strange things happen when we step-by-step through these lines.
For example, instead of showing:
"// Não temos nenhum nó, garante não ter um falso ponteiro"
in the source window, gdbtui shows:
"// NM-CM-#o temos nenhum nM-CM-3, garante nM-CM-#o ter um falso ponteiro"
The environment is correctly set:
$ set | grep -e 'LANG|LC_ALL'
LANG=pt_BR.UTF-8
LANGUAGE=pt_BR.UTF-8:en_GB:en
LC_ALL=pt_BR.UTF-8
How can I make gdbtui work correctly? If no answer exist for this question, I may help filling a bug report about it. I will need a bit of help with that, please offer, if that is possible.
next parent reply other threads:[~2017-10-18 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1311475292.483858.1508348766742.ref@mail.yahoo.com>
2017-10-18 17:50 ` Dedeco Balaco Baco via gdb [this message]
2017-10-18 18:37 ` Simon Marchi
2017-10-19 2:22 ` Dedeco Balaco via gdb
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311475292.483858.1508348766742@mail.yahoo.com \
--to=gdb@sourceware.org \
--cc=dedeco.balaco@yahoo.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox