From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: coding system and gdb
Date: Wed, 8 Jul 2015 10:09:55 -0700 (PDT) [thread overview]
Message-ID: <55cb5ba9-0f21-40c5-9bd9-dd6d1286b419@googlegroups.com> (raw)
In-Reply-To: <mailman.6562.1436374619.904.help-gnu-emacs@gnu.org>
On Wednesday, July 8, 2015 at 10:27:02 PM UTC+5:30, Eli Zaretskii wrote:
> > Date: Wed, 8 Jul 2015 09:23:39 -0700 (PDT)
> > From: Rusi
> >
> > Some students of mine are working on a hand-compiled python and debugging with gdb in emacs.
> > Unicode characters dont seem to be flowing properly between (inferior) python and
> > emacs; seems to work better when python is started outside emacs.
> >
> > Is there some process-related-coding-system that is to be set for gdb?
> >
> > How/When/Where?
>
> Please provide some minimal details about the GDB commands you tried,
> and their results. GDB is generally agnostic to encoding issues, it's
> all just data for it, so I'm having hard time guessing what exactly
> didn't work for your students.
>
> In general, process-coding-system-alist is the feature you are
> supposed to use to set up encoding for communicating with processes,
> in case the locale's defaults aren't TRT.
I'll find out more details and repost.
For now Ive this mail from them:
--------
I tried a='ब' in emacs gdb but it is interpreting it as. a= ' ' and it is not
printing anything when we do print(a) but it is printing correctly in terminal
with our compiled python.
next prev parent reply other threads:[~2015-07-08 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 16:23 coding system and gdb Rusi
2015-07-08 16:56 ` Eli Zaretskii
[not found] ` <mailman.6562.1436374619.904.help-gnu-emacs@gnu.org>
2015-07-08 17:09 ` Rusi [this message]
2015-07-08 19:44 ` Eli Zaretskii
2015-07-08 17:47 ` tomas
2015-07-08 19:47 ` Eli Zaretskii
[not found] ` <mailman.6568.1436377660.904.help-gnu-emacs@gnu.org>
2015-07-09 17:11 ` Rusi
2015-07-09 17:39 ` Eli Zaretskii
[not found] ` <mailman.6623.1436463582.904.help-gnu-emacs@gnu.org>
2015-07-11 17:01 ` Rusi
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=55cb5ba9-0f21-40c5-9bd9-dd6d1286b419@googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).