Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Configuring gdb_wchar.h
Date: Tue, 14 Apr 2009 17:11:00 -0000	[thread overview]
Message-ID: <83myajma7a.fsf@gnu.org> (raw)
In-Reply-To: <m3iql7jiy6.fsf@fleche.redhat.com>

> Cc: gdb-patches@sources.redhat.com
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 14 Apr 2009 10:31:13 -0600
> 
> If you have dejagnu, try charset.exp.

I don't (dejagnu doesn't work on DOS), but I can easily run the same
test manually.

> Otherwise, any use of a string in an expression should exercise the
> relevant code paths.  You could also "set target-charset" and see what
> gdb thinks is available; if you have libiconv there should be lots of
> output.

Something's definitely wrong, because "set target-charset TAB" just
beeps, and if I type RET, it says:

    (gdb) set target-charset
    Requires an argument. Valid arguments are .

So it thinks there are no charsets available.  Maybe the line marked
below, shown as part of GDB initialization, is a hint to the trouble:

       D:\gdb-68.410\gdb>gdb ./gdb.exe
 >>>>  Usage: iconv [--binary] [-f fromcode] [-t tocode] [file ...]
       GNU gdb (GDB) 6.8.50.20090410
       Copyright (C) 2009 Free Software Foundation, Inc.

I will look into it.  Thanks for the leads.


  reply	other threads:[~2009-04-14 17:11 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 [this message]
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
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=83myajma7a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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