Hi.

I don't actually use bash myself - so something that would be apparent
to a bash user is invisible to me.

As part of the packaging of bash-5.0.18 (i.e., 5.0 at patch level 18) I
ran the test suite.

a) is there a flag I can pass so that it ignores the UTF-8 tests? I do
not want to not build UTF-8 support - for anyone who does load those
language filesets, but I would prefer to not see that test show up as
failed - rather as skipped.

b) I have - apparently - been a LONG time since I last ran `make test`
for bash, as I get the same error on bash-4.4 patch level 23, and on
bash-5.0 patch level 11 and bash-5.0 patch level 18.

run-vredir
14,16c14,16
< ./vredir.tests: line 25: $v: A file descriptor does not refer to an
open file.
< ./vredir.tests: line 26: $v: A file descriptor does not refer to an
open file.
< ./vredir.tests: line 27: $v: A file descriptor does not refer to an
open file.
---
> ./vredir.tests: line 25: $v: Bad file descriptor
> ./vredir.tests: line 26: $v: Bad file descriptor
> ./vredir.tests: line 27: $v: Bad file descriptor
90,91c90,91
< ./vredir6.sub: redirection error: cannot duplicate fd: The process
file table is full.
< ./vredir6.sub: line 13: /dev/null: The process file table is full.
---
> ./vredir6.sub: redirection error: cannot duplicate fd: Invalid argument
> ./vredir6.sub: line 13: /dev/null: Invalid argument
root@x065:[/data/prj/gnu/bash/bash-4.4.23]

To try and understand what is going on - I ran the following commands
from the CLI. I hope you can give me some suggestions on what to look at.

```

root@x065:[/data/prj/gnu/bash/bash-5.0.18]./bash
root@x065:[/data/prj/gnu/bash/bash-5.0.18]PS1='$ '
$ unset v
$ exec {v}</dev/null
$ echo $v
10
$ exec {v}<&-
$ ulimit -n
20000
$ ulimit -n 6
$ ulimit -n
6
$ exec </dev/null
$ exit
root@x065:[/data/prj/gnu/bash/bash-5.0.18]

```

As you can see by the return of the original PS1 - the sub-shell
(./bash) 'crashed' -- I did not type 'exit' - that is a result of the
'exec </dev/null' command the line before.

Hope this helps,

Michael (aka aixtools).



Reply via email to