From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Configuring gdb_wchar.h
Date: Wed, 15 Apr 2009 15:08:00 -0000 [thread overview]
Message-ID: <m3zleigdk2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8363h6mdue.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 15 Apr 2009 13\:05\:29 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> It builds fine, but the result seems strange to me: GDB now lists a
Eli> long list of character sets in response to "set target-charset TAB".
Eli> What happens is that find_charset_names correctly notices that
Eli> "iconv -l" exited with a non-zero status (this is still with libiconv 1.7,
Eli> where the -l switch is not supported), but then _initialize_charset
Eli> falls back on using DEFAULT_CHARSET_NAMES, which seem to assume a
Eli> glibc-based system. I rather expected the result to be that only a
Eli> single target charset be available. Am I missing something? Should
Eli> DEFAULT_CHARSET_NAMES be redefined on DJGPP to something different
Eli> from what charset-list.h defines it?
Your situation is somewhat odd. You have a working iconv but no way
to get a list of available character sets. This ought to be a rare
setup.
In this case I chose to make gdb fall back on a fairly large built-in
list. If you try pick a charset which your iconv cannot handle, gdb
should give an error.
Eli> I will upgrade to a newer libiconv and try with that, once the result
Eli> for 1.7 is as expected (whatever that might be).
I think the current result is as good as any other.
Tom
next prev parent reply other threads:[~2009-04-15 15:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 17:53 Eli Zaretskii
2009-04-13 17:54 ` Tom Tromey
2009-04-14 12:03 ` Eli Zaretskii
2009-04-14 16:31 ` Tom Tromey
2009-04-14 17:11 ` Eli Zaretskii
2009-04-14 17:42 ` Tom Tromey
2009-04-14 18:04 ` Eli Zaretskii
2009-04-14 18:15 ` Tom Tromey
2009-04-14 20:17 ` Eli Zaretskii
2009-04-15 0:23 ` Tom Tromey
2009-04-15 10:06 ` Eli Zaretskii
2009-04-15 14:01 ` Eli Zaretskii
2009-04-15 15:14 ` Tom Tromey
2009-04-15 15:33 ` Eli Zaretskii
2009-04-15 18:04 ` Tom Tromey
2009-04-15 19:20 ` Eli Zaretskii
2009-04-15 19:53 ` Tom Tromey
2009-04-15 20:18 ` Eli Zaretskii
2009-04-18 9:47 ` Eli Zaretskii
2009-04-18 17:28 ` Tom Tromey
2009-04-19 18:30 ` Eli Zaretskii
2009-04-15 15:08 ` Tom Tromey [this message]
2009-04-15 15:12 ` Pedro Alves
2009-04-15 15:26 ` Tom Tromey
2009-04-15 15:47 ` Eli Zaretskii
2009-04-15 18:07 ` Tom Tromey
2009-04-15 22:13 ` Tom Tromey
2009-04-18 11:05 ` Eli Zaretskii
2009-04-18 17:34 ` Tom Tromey
2009-04-18 20:56 ` 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=m3zleigdk2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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