From: Duane Ellis <duane@duaneellis.com>
To: gdb@sourceware.org
Subject: re: gdb support for wide char
Date: Wed, 15 Oct 2008 00:14:00 -0000 [thread overview]
Message-ID: <48F535CF.60300@duaneellis.com> (raw)
In-Reply-To: <1224016294.17588.ezmlm@sourceware.org>
Yifan> and now i am working on utf8 which is not fixed length character.
Yifan> The solution rely on the glibc functions, eg.mbstowcs(), iconv(), to
Yifan> support wide character.
Yifan> I dont know whether this solution is good enough, because it
Yifan> does not support other programming language and it rely on the
Yifan> glibc functions.
tom> Is it calling these functions in the inferior?
I would hope not - because many inferiors *DO*NOT* have those functions.
Examples:
1) Embedded systems. There are countless ones out there.
2) Or - when you are debugging on Host (A) talking to Host (B) which
is a vastly different operating system.
The solution must be 100% self contained within GDB, requiring ZERO
target support other then raw memory bytes to display.
-Duane.
next parent reply other threads:[~2008-10-15 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1224016294.17588.ezmlm@sourceware.org>
2008-10-15 0:14 ` Duane Ellis [this message]
2008-10-01 10:29 Yifan Wang
2008-10-01 15:28 ` Tom Tromey
2008-10-13 8:56 ` Yifan Wang
2008-10-13 18:48 ` Tom Tromey
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=48F535CF.60300@duaneellis.com \
--to=duane@duaneellis.com \
--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