Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, fnasser@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Spurious testsuite failures due to multibyte locale
Date: Mon, 06 Jan 2003 18:17:00 -0000	[thread overview]
Message-ID: <15897.51499.389985.860056@localhost.redhat.com> (raw)
In-Reply-To: <20030105173513.GA2779@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Sun, Jan 05, 2003 at 11:28:51AM -0600, Michael Elizabeth Chastain wrote:
 > > Andreas Schwab writes:
 > > > I'm getting numerous spurious testsuite failures when running in a
 > > > multibyte locale like utf8 because the version of readline included in
 > > > gdb forces the command line to be always redrawn completely when
 > > > running in a multibyte locale.  The output of the prompt will look
 > > > like "\r\n\r\r(gdb) \r(gdb) " which won't be matched by $gdb_prompt.
 > > 
 > > Me too:
 > > 
 > >   http://sources.redhat.com/ml/gdb-patches/2002-12/msg00294.html
 > > 
 > > At first I thought it was an artifact of my test bed configuration, but
 > > I've straightened out my test bed and it still happens.  This is with
 > > host=i686-pc-linux-gnu, osversion=red-hat-8.0, with $LANG=en_us.UTF-8.
 > > 
 > > I work around it now by setting $LANG=en_us when I run the test suite.
 > > 
 > > > -# Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000
 > > > +# Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2003
 > > 
 > > As long as you are touching this line, can you add 2001 and 2002
 > > to the copyright years?  I checked "cvs log gdb.exp" and there
 > > were plenty of changes during those two years.
 > 
 > Did this yesterday :)
 > 
 > > > +# Make sure we are using the C locale.
 > > > +set env(LC_ALL) "C"
 > > > +
 > > 
 > > Seems okay to me but I don't have the resources to test it right now.
 > > 
 > > I've appended my brain dump just in case anyone is curious.
 > > It's on my TODO list to write a small "readline" test program and
 > > file a bug report with the readline maintainers.
 > 
 > I'm inclined to agree.  Tests which want to test something locale
 > related can do so explicitly.  Andreas, if no one objects in the next
 > day or so, please check this in.
 > 
 > 

I am not objecting at all, but I think Fernando should have the last
word. Not that I think he will object either...

Elena

 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-06 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 17:29 Michael Elizabeth Chastain
2003-01-05 17:35 ` Daniel Jacobowitz
2003-01-06 18:17   ` Elena Zannoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06  1:18 Michael Elizabeth Chastain
2003-01-05 17:05 Andreas Schwab

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=15897.51499.389985.860056@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --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