From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Andre Oliveira Loureiro do Baixo <andreolb@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Thu, 12 Mar 2009 01:11:00 -0000 [thread overview]
Message-ID: <m3d4cny9y3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3ljrbybmc.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed\, 11 Mar 2009 15\:48\:27 -0600")
Tom> The difficulty is really in deciding the way forward. I don't know
Tom> what to do.
Just to be clear, here are the issues that I know of.
* The patch assumes that iconv recognizes "wchar_t" as a charset name.
I have read that this is not universally true, but I have not tested
this. I'd be interested in reports on this from folks on non-Linux
hosts.
* What to do about hosts without an iconv implementation. There are
three choices:
1. Require libiconv on such hosts
2. Like #1, but provide a simple way to drop libiconv into the src
tree.
3. Write a phony iconv-alike that only handles host charset ==
target charset, probably also providing "gdb_wchar_t" and various
other macros and whatnot to make it all work.
Related to this is the question of what to do if we run into a host
that has a notably bad iconv.
These are roughly in the order in which I'd prefer to do them... but
then, the problem does not actually affect any machine I have access
to.
* I'd like comments on this patch (scroll to the end):
http://sourceware.org/ml/gdb-patches/2009-01/msg00363.html
It helps with the C case, and IMO at least creates types more along
the lines of what I would expect. But, I'm not an expert here and I
also don't know whether a similar patch is needed for the stabs
reader.
Tom
next prev parent reply other threads:[~2009-03-11 22:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30 ` Daniel Jacobowitz
2009-03-11 17:09 ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13 ` Tom Tromey
2009-03-11 18:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29 ` Thiago Jung Bauermann
2009-03-11 22:25 ` Tom Tromey
2009-03-12 1:11 ` Tom Tromey [this message]
2009-03-13 23:37 ` Joel Brobecker
2009-03-13 23:38 ` Joel Brobecker
2009-03-14 1:41 ` Tom Tromey
2009-03-14 0:10 ` Mark Kettenis
2009-03-17 20:06 ` Tom Tromey
2009-03-17 22:12 ` Eli Zaretskii
2009-03-18 3:07 ` Tom Tromey
2009-03-18 4:20 ` Eli Zaretskii
2009-03-18 17:11 ` Tom Tromey
2009-03-18 20:30 ` Eli Zaretskii
2009-03-18 0:46 ` Joel Brobecker
2009-03-18 1:14 ` 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=m3d4cny9y3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andreolb@gmail.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@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