[Bash-completion-devel] [bash-completion-Bugs][312477] _filedir unit test fails in C locale with bash 4.1.x, with any locale with bash 3.2.x
bash-completion-bugs at alioth.debian.org
bash-completion-bugs at alioth.debian.org
Tue Oct 19 20:51:17 UTC 2010
Bugs item #312477, was changed at 2010-04-26 18:35 by Freddy Vulto
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312477&group_id=100114
Status: Open
Priority: 3
Submitted By: Ville Skyttä (scop-guest)
Assigned to: Nobody (None)
Summary: _filedir unit test fails in C locale with bash 4.1.x, with any locale with bash 3.2.x
Distribution: None
Originally reported in: None
Milestone: None
Status: None
Original bug number:
Initial Comment:
With my usual setting (LANG=en_US.UTF-8) it passes, but:
$ LANG=C ./runUnit _filedir.exp
WARNING: Couldn't find the global config file.
Test Run By scop on Mon Apr 26 19:33:04 2010
Native configuration is x86_64-unknown-linux-gnu
=== unit tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/default.exp as tool-and-target-specific interface file.
Running ./unit/_filedir.exp ...
FAIL: f aé/ should show completions at timeout
FAIL: f aé/ should show completions
=== unit Summary ===
# of expected passes 46
# of unexpected failures 2
/home/scop/cvs/bash-completion/test, bash-4.1.2(1)-release
----------------------------------------------------------------------
>Comment By: Freddy Vulto (fvu-guest)
Date: 2010-10-19 22:51
Message:
Hmm, and on another Ubuntu-10.04 this test is giving me a segmentation fault right after the aé test seemed to have passed... Can you run the test with --debug and send the part of dbg.log where the test fails?
----------------------------------------------------------------------
Comment By: Ville Skyttä (scop-guest)
Date: 2010-10-18 23:14
Message:
Unfortunately that change does not appear to make any difference here; it behaves just like before it (fails with en_US.UTF-8 with both bash 3.2.25 and 3.2.39, works with 4.1.7).
----------------------------------------------------------------------
Comment By: Freddy Vulto (fvu-guest)
Date: 2010-10-18 22:31
Message:
I'm having troubles with `expect': changing the locale within an `expect'
session causes bash to exit, although I had it working before. The problem
occurs only on an old Debian system though, not on a newer Ubuntu system...
Steps to reproduce the problem:
1. Create a file unicode.exp containing:
spawn bash
send "LC_CTYPE=C\r"
send "aaébb"; # unicode é = \u00e9
expect -ex "cc"; # 'expect' detects eof when reading \u00e9?
send "dd"; # 'expect' error: spawn id not open
2. Run: LC_CTYPE=en_US.UTF-8 expect -f unicode.exp
3. I get this error output:
$ expect -f unicode.exp
spawn bash
LC_CTYPE=C
aaébb$ LC_CTYPE=C
$ aasend: spawn id exp6 not open
while executing
"send "dd""
(file "unicode.exp" line 6)
4. What I expected is the same output as with LC_CTYPE=C expect -f unicode.exp:
$ LC_CTYPE=C expect -f unicode.exp
spawn bash
LC_CTYPE=C
aaébb$ LC_CTYPE=C
$ aaC)bb$
See also: http://fvue.nl/wiki/Expect:_Changing_locale_causes_spawned_process_to_exit
So it looks like changing LC_CTYPE within `expect' wasn't such a good idea.
For now I'll put the _filedir test ("completing f aé should return g") behind
the condition that LC_CTYPE should match *UTF-8*, otherwise the following run
definitely fails:
$ LC_CTYPE=C ./run unit/_filedir.exp
See commit 37f51b9.
Greetings,
Freddy Vulto
http://fvue.nl
----------------------------------------------------------------------
Comment By: Freddy Vulto (fvu-guest)
Date: 2010-10-11 22:13
Message:
Don't know what's going on. I get your errors when running from cron. But when running manual with locale set to "en_US.UTF-8", tcl/expect/dejagnu chokes on the unicode char, from dbg.log:
send: sending "f a\u00e9/\t" to { exp9 }
expect: does "" (spawn_id exp9) match exact string "f a\u00e9/"? no
f
expect: does "f" (spawn_id exp9) match exact string "f a\u00e9/"? no
expect: does "f " (spawn_id exp9) match exact string "f a\u00e9/"? no
a
expect: does "f a" (spawn_id exp9) match exact string "f a\u00e9/"? no
expect: read eof
expect: set expect_out(spawn_id) "exp9"
expect: set expect_out(buffer) "f a"
write() failed to write anything - will sleep(1) and retry...
ERROR: tcl error sourcing ./unit/_filedir.exp.
ERROR: expect: spawn id exp9 not open
----------------------------------------------------------------------
Comment By: Ville Skyttä (scop-guest)
Date: 2010-10-10 10:53
Message:
It also fails the same way for me with bash 3.2.25 and 3.2.39, no matter what LANG is set to.
----------------------------------------------------------------------
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=312477&group_id=100114
More information about the Bash-completion-devel
mailing list