Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] defs.h: Define GDB_DEFAULT_TARGET_[WIDE_]CHARSET for   Cygwin  and MingW builds
Date: Tue, 02 Mar 2010 10:44:00 -0000	[thread overview]
Message-ID: <20100302104358.GA26083@calimero.vinschen.de> (raw)
In-Reply-To: <20100301215033.GB17815@caradoc.them.org>

On Mar  1 16:50, Daniel Jacobowitz wrote:
> On Mon, Mar 01, 2010 at 10:44:43PM +0200, Eli Zaretskii wrote:
> > It sounds like, for cross debugging, the only fair default is ASCII.
> > That way, each user will have to set the right target charset, and no
> > one will feel they are children of a lesser god.
> 
> This is a target specific setting.  Why is there so much resistance to
> making the target set the property?  This is how we handle lots of our
> other global and target-related state.
> 
> There's a function, target_wide_charset.  It is currently passed a
> byte order, and consults various globals.  It should be passed a
> gdbarch instead of a byte order, which will require some refactoring
> but nothing major from my inspection.  That's one straightforward
> patch.
> 
> target_wide_charset_name can not currently be set to auto.  That
> should be allowed, and the default; if it is "auto", then it should
> be returned (and "show target-wide-charset" too) as
> GDB_DEFAULT_TARGET_WIDE_CHARSET.  Just like host_charset_name /
> auto_host_charset name.  That's another straightforward patch.

This, as well as the same for target_charset_name was already in
my previous patch.

But I don't see a reason to keep the auto_target_wide_charset_name and
auto_target_charset_name variables since they would be entirely replaced
by the gdbarch equivalent...

> Then, GDB_DEFAULT_TARGET_WIDE_CHARSET can become a gdbarch variable.
> The gdbarch created in i386_cygwin_init_abi can set it to the right
> thing.  The default can be what it is now.  This patch is less
> straightforward because of the existing hacks, like PHONY_ICONV.

The target specifies charset and wide charset.  So we need two
target-specific variables.  As I mentioned above, both variables would
replace the auto_target...charset variables.

I know how to change gdbarch.sh to add the variables, and I have
all the other stuff almost in place.  But I have a problem.

How do I access the current gdbarch from show_target_charset_name,
show_target_wide_charset_name, and all the other functions in charset.c
which refer to the target charsets?


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat


  reply	other threads:[~2010-03-02 10:44 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 13:05 Corinna Vinschen
2010-02-28 14:29 ` Daniel Jacobowitz
2010-02-28 15:03   ` Corinna Vinschen
2010-02-28 18:48     ` Daniel Jacobowitz
2010-02-28 19:22       ` Corinna Vinschen
2010-02-28 22:27         ` Daniel Jacobowitz
2010-03-01 10:31           ` Corinna Vinschen
2010-03-01 17:11             ` Eli Zaretskii
2010-03-01 17:28               ` Corinna Vinschen
2010-03-01 17:21             ` Tom Tromey
2010-03-01 17:23               ` Daniel Jacobowitz
2010-03-01 17:27                 ` Corinna Vinschen
2010-03-01 17:31               ` Corinna Vinschen
2010-03-01 19:25                 ` Tom Tromey
2010-03-01 19:31                   ` Daniel Jacobowitz
2010-03-01 20:06                     ` Corinna Vinschen
2010-03-01 20:44                     ` Eli Zaretskii
2010-03-01 21:50                       ` Daniel Jacobowitz
2010-03-02 10:44                         ` Corinna Vinschen [this message]
2010-03-02 13:54                           ` Daniel Jacobowitz
2010-03-02 14:13                             ` Corinna Vinschen
2010-03-02 15:03                               ` Daniel Jacobowitz
2010-03-02 17:43                                 ` Corinna Vinschen
2010-03-02 17:59                     ` Tom Tromey
2010-03-02 18:22                       ` Corinna Vinschen
2010-03-02 18:28                         ` Corinna Vinschen
2010-03-02 22:55                       ` Tom Tromey
2010-03-02 22:57                         ` Tom Tromey
2010-03-03 10:16                           ` Corinna Vinschen
2010-03-03 10:41                             ` Corinna Vinschen
2010-03-03 10:59                               ` Corinna Vinschen
2010-03-03 16:26                                 ` Tom Tromey
2010-03-03 10:16                         ` Corinna Vinschen
2010-03-03 16:25                           ` Tom Tromey
2010-03-03 16:46                             ` Corinna Vinschen
2010-03-05  8:55                               ` Charles Wilson
2010-03-03 21:15                           ` Tom Tromey
2010-03-04  9:34                             ` Corinna Vinschen
2010-03-04 15:24                               ` Christopher Faylor
2010-03-04 15:38                                 ` Corinna Vinschen
2010-03-03 17:08                         ` Daniel Jacobowitz
2010-03-03 17:22                           ` Corinna Vinschen
2010-03-03 17:27                             ` Corinna Vinschen
2010-03-03 17:33                             ` Daniel Jacobowitz
2010-03-03 17:42                               ` Eli Zaretskii
2010-03-03 18:00                               ` Corinna Vinschen
2010-03-03 18:05                                 ` Daniel Jacobowitz
2010-03-03 18:22                                   ` Corinna Vinschen
2010-03-03 19:39                                     ` Daniel Jacobowitz
2010-03-03 20:16                                       ` Eli Zaretskii
2010-03-03 20:26                                         ` Daniel Jacobowitz
2010-03-03 21:08                           ` Tom Tromey
2010-03-01 17:12           ` Tom Tromey
2010-03-01 17:21             ` Daniel Jacobowitz
2010-03-01 17:28               ` Tom Tromey
2010-03-01 17:50                 ` Corinna Vinschen
2010-02-28 16:56 ` Eli Zaretskii
2010-02-28 17:05   ` Corinna Vinschen
2010-02-28 17:45     ` Eli Zaretskii
2010-02-28 17:52       ` Corinna Vinschen
2010-02-28 18:11         ` Corinna Vinschen
2010-02-28 18:59           ` Eli Zaretskii
2010-02-28 19:23             ` Corinna Vinschen
2010-02-28 18:59         ` 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=20100302104358.GA26083@calimero.vinschen.de \
    --to=vinschen@redhat.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