From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: GDB/MI reporting non-ASCII file names
Date: Wed, 30 Sep 2015 14:49:00 -0000 [thread overview]
Message-ID: <560BF686.1030400@redhat.com> (raw)
In-Reply-To: <83bnckasck.fsf@gnu.org>
On 09/30/2015 03:34 PM, Eli Zaretskii wrote:
>> Date: Wed, 30 Sep 2015 12:52:25 +0100
>> From: Pedro Alves <palves@redhat.com>
>>
>> I happened to stumble on this discussion yesterday:
>>
>> https://www.sourceware.org/ml/gdb/2012-03/msg00001.html
>>
>> Which points at:
>>
>> https://sourceware.org/ml/gdb/2010-08/msg00129.html
>
> Thanks. So it's hard-wired in MI, and the grammar requires that. Too
> bad.
We can always extend it. Maybe we just need to document that ascii is
the default, and that frontends should
issue -gdb-set print sevenbit-strings off if they want non-ascii?
Seems like Eclipse ended up doing that.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-09-30 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 9:18 Eli Zaretskii
2015-09-30 11:52 ` Pedro Alves
2015-09-30 14:34 ` Eli Zaretskii
2015-09-30 14:49 ` Pedro Alves [this message]
2015-09-30 15:52 ` Eli Zaretskii
2015-10-09 11:12 ` Pedro Alves
2015-10-09 13:31 ` Eli Zaretskii
2015-10-09 16:48 ` Pedro Alves
2015-10-09 17:11 ` Eli Zaretskii
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=560BF686.1030400@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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