| No. |
VSC-lite Testcase Where The Bug Was Detected |
POSIX 1003.2 |
Status |
The Bug |
| VSC-lite |
Bash-2.05 |
| 1 |
sh_04 277 |
When a shell is reading input from a file and the current character is an
unquoted <newline>, '\n', the current token shall be delimited.
|
N/A
To be fixed
Bash: Does not recognize unquoted <newline> as a token delimiter when inputs
from a file. Exit status 127 was received.
|
| |
| 2 |
sh_05 293 |
When a variable has been assigned a value (including the null value), then the
variable is set and can only be unset by use of the unset special built-in.
|
Outstanding
Outstanding
| There is a differnce in interpretations of the POSIX 1003.2 standard between the VSC-lite developers and
Bash current maintainer as to whether or not the set builtin comand should include functions when set is invoked with
no options. Mr. Andrew Josey will file a POSIX 1003.2 interpretation request to the IEEE
to see whether the bash extension is compliant. |
| |
| 3 |
sh_05 303 |
The special parameter '-' expand to the current set of option flags set for the
shell. The flags can be specified on invocation, by the set command or implicitly
by the shell.
|
N/A
To be fixed.
Bash: looses some of the set option flags when echo $- back.
|
| |
| 4 |
sh_05 334 |
When the value of the variable parameter is unset or null and the _expression_
${parameter:?word} is encountered, then the value of word after being subjected
to tilde expansion, parameter expansion, command substitution and arithmetic
expansion is written to the standard error and a non- interactive shell exits
with a non-zero exit status.
|
N/A
To be fixed
|
Bash: exits the non-interactive with a zero exit status instead of with
a non-zero exit status.
|
| |
| 5 |
sh_05 335 |
When the value of parameter is unset or null and the _expression_ ${parameter:?}
is encountered, then a message indicating that parameter is unset is written to
the standard error and a non-interactive shell exits with a non-zero exit status.
|
N/A
To be fixed.
|
Bash: Non-interactive shell exits with a zero exit status instead of with
a non-zero exit status.
|
| |
| 6 |
sh_05 343 |
When the value of parameter is unset and the _expression_ ${parameter?word} is
encountered, then the value of word after being subjected to tilde expansion,
parameter expansion, command substitution and arithmetic expansion shall be
written to the standard error and a non-interactive shell exits with a non-zero
exit status.
|
N/A
To be fixed
|
Bash: Non-interactive shell exits with a zero exit status instead of with
a non-zero exit status.
|
| |
| 7 |
sh_05 344 |
When the value of the variable parameter is unset and the _expression_ ${parameter?word}
is encountered, then a message indication that parameter is unset is written to standard
error and a non-interactive shell exits.
|
N/A
To be fixed
|
Bash: Non-interactive shell exits with a zero exit status instead of with
a non-zero exit status
|
| |
| 8 |
sh_05 357 |
The resulting _expression_ derived from $((_expression_)) is evaluated according to the rules
for Arithmetic Precision and Operations, subject to the exceptions given in POSIX.2 {9},
and substitutes the resulting value for the _expression_.
|
To be fixed
N/A
|
Testsuite: accessing value of a variable without using $ in front of a variable
(e.g., [ x -eq 2 ] instead of [$x -eq 2]).
|
| |
| 9 |
sh_05 358 |
When the arithmetic _expression_ obtained from expanding $((_expression_)) is invalid, then the
shell prints a message to standard error indicating the failure.
|
N/A
To be fixed
|
Bash: writes error message but does not exit non-interactive shell.
|
| |
| 10 |
sh_05 364 |
When the value of IFS consists of a combination of white space characters and other characters, then any sequence of
zero or more of the IFS white space characters with a single occurrence of one of the other IFS characters shall serve as
a single delimiter to delimit a field.
|
N/A
To be fixed
|
Bash: using a non-white-space IFS character adjacent to any sequence of
IFS white space as two delimiters instead of one.
|
| |
| 11 |
sh_06 378 |
GA10 - When a file is newly created by the $CATCREATEOUT utility, then the file attributes
are set as follows:
(1) The file's user ID is set to the effective user ID of the creating process.
(2) The file's group ID is set to either the effective group ID of the creating process
or to the group ID of the directory in which the file is created.
(3) The file's permission bits are set to S_IROTH|S_IWOTH|S_IRGRP|S_IWGRP|S_IRUSR|S_IWUSR except that
the bits set in the creating processes file mode creation mask are cleared.
(4) The st_atime, st_ctime and st_mtime fields of the file are updated
(5) When the file is a directory, then the directory is created empty.
(6) When the file is not a directory, then it has zero length.
(7) When the file type is not specified, then a regular file is created.
|
To be determined
N/A
|
Testsuite: unable to locate GetFileData which is supposed to come with
the test suite.
|
| |
| 12 |
sh_06 379 |
When a file that exists is re-created by a POSIX.2 application, then the file attributes are set as follows:
(1) When the file type is a directory or FIFO special file, then the attempt fails and the file attributes are not changed.
(2) When the file type is a regular file, then the file is truncated to zero length and the st_ctime and st_mtime fields are
updated. The user-ID, group-ID and permission bits associated with the file are unchanged.
|
To be determined
N/A
|
Testsuite: unable to locate GetFileData which is supposed to come with
the test suite.
|
| |
| 13 |
sh_06 413 |
The redirection operator [n]<>word shall cause the file whose name is the expansion of word to be opened for both
reading and writing on the file descriptor denoted by n, or standard input if n is not specified. If the file does not exist, it
shall be created.
|
N/A
To be fixed
|
Bash: { echo hello <> xxx 1>&0 } generates empty xxx file instead a xxx file
with hello in it as the test suite expects.
|
| |
| 14 |
sh_06 425 |
When a 'dot' script is not found by the shell, then the shell writes a diagnostic message to standard error and exits with a
non-zero status.
|
N/A
To be fixed
|
Bash: writes diagnostic error message but does not exit subshell with
non-zero status.
|
| |
| 15 |
sh_07 433 |
When a simple command is required to be executed, then the words that are not variable assignments or redirections are
expanded. The first remaining field, if any, is considered the command name and the remaining fields are operands for
the command.
|
N/A
To be fixed
|
Bash: Unable to define and use an alias in a non-interactive shell;
therefore, bash produces erroneous results.
|
| |
| 16 |
sh_07 435 |
When a search for a command in PATH results in no matching command name, then the variable assignments affect the
current execution environment.
|
N/A
To be fixed
|
Bash: Unable to define and use an alias in subshell; therefore, bash
produces erroneous results.
|
| |
| 17 |
sh_07 436 |
When a command name results, then the variable assignments are exported for the execution environment of the
command and do not affect the current execution environment.
|
N/A
To be fixed
|
Bash: Unable to define and use an alias in subshell; therefore, bash
produces erroneous results.
|
| |
| 18 |
sh_07 437 |
When a variable assignment attempts to assign a value to a readonly variable, then the command immediately fails with
an exit status greater than zero. The shell prints an error message to standard error indicating the failure.
|
N/A
To be fixed
|
Bash: does not exit subshell nor returns a non-zero exit status.
|
| |
| 19 |
sh_07 441 |
When no command name is generated and no command substitution occurred, then the exit status is zero.
|
N/A
To be fixed
|
Bash: exit status 127: unable to define/use an alias in a subshell.
|
| |
| 20 |
sh_07 444 |
When the command name does not contain any slashes and the command name does not match any special built-in or
any function but does match a regular built-in utility specified in POSIX.2 {9} 2.3, then the built-in utility is invoked.
|
N/A
To be fixed
|
Bash: error: command not found: unable to define and use an alias
in a subshell.
|
| |
| 21 |
sh_07 448 |
When the search for command name using the PATH environment variable succeeds, then the command is executed
with actions equivalent to calling 'execve()' with the path argument set to the pathname resulting from the search, 'argv[0]'
set to the command name and the remaining arguments set to the operands.
|
N/A
Intentional Exception
|
Bash: gives full path to command name(/xx/yy/script) for $0 in subshell
instead of just command name(script).
|
| |
| 22 |
sh_07 449 |
When the search for command name using the PATH environment variable succeeds and the 'execve()' function fails
with an ENOEXEC error condition, then the shell executes a command equivalent to invoking the shell with the name of
the command as its first operand followed by any shall remaining operands.
|
N/A
To be fixed
|
Bash: gives full path to command name(/xx/yy/script) for $0 in subshell
instead of just command name(script).
|
| |
| 23 |
sh_08 461 |
The special parameter $! expands to the process ID of the last command in an asynchronous list.
|
To be fixed
N/A
|
Testsuite: use print command in a script.
|
| |
| 24 |
sh_08 462 |
The process ID of the last command in an asynchronous list shall remains available to the shell (via the special parameter
$!) until the shell executes a wait command, or another asynchronous list is invoked before $! is expanded in the current
execution environment.
|
To be fixed
N/A
|
Testsuite: use print command in a script.
|
| |
| 25 |
sh_08 474 |
Variable assignments and built-in commands that affect the environment do not shall remain in effect after the (list)
finishes.
|
Outstanding
Outstanding
|
There is a differnce in interpretations of the POSIX 1003.2 standard between the VSC-lite developers and
Bash current maintainer as to whether or not the set builtin comand should include functions when set is invoked with
no options. Mr. Andrew Josey will file a POSIX 1003.2 interpretation request to the IEEE
to see whether the bash extension is compliant.
|
| |
| 26 |
sh_08 478 |
The commands executed in the for loop are delimited by the words do and done.
|
To be fixed
N/A
|
Testsuite: use print command in a script.
|
| |
| 27 |
sh_08 479 |
The list of words following 'in' in the for loop shall expand to generate a list of words
|
To be fixed
N/A
|
Testsuite: use print command in a script.
|
| |
| 28 |
sh_09 517 |
When a word expansion error occurs during a call to a
function, then a non-interactive shell aborts.
|
N/A
To be fixed
|
Bash: does not abort non-interactive shell when redirection error occurs with
special built-in command eval.
|
| |
| 29 |
sh_09 529 |
Each command in a multi-command pipeline is executed in a
subshell environment.
|
N/A
To be fixed
|
Bash: executes other built-in commands in subshells.
|
| |
| 30 |
sh_09 530 |
All other commands, ( other than command substitution, grouped commands in parentheses, and
asynchronous lists) including the shell built-ins, are executed in the current shell
environment.
|
N/A
To be fixed
|
Bash: executes other built-in commands in subshells.
|
| |
| 31 |
sh_09 532 |
When used outside a bracket _expression_ and immediately preceded by
a backslash each of the characters '|', '&', ';', '<', '>',
'(', ')', '$', '`', '\', '"', "'", '', '', '',
'?', '*', or '[' matches itself.
|
To be fixed
N/A
|
Testsuite: syntax error when trying to create a shell script(e.g., using \\& instead
of \&).
|
| |
| 32 |
sh_09 538 |
A right bracket represents itself in a bracket _expression_ when one
of the following is true:
(1) it occurs first in the list
(2) it occurs first in the list after an initial
exclamation mark ('!')
(3) it appears in a collating symbol
(4) it is the ending right bracket of a collating symbol,
equivalence class, or character class.
|
N/A
To be fixed
|
Bash: does not recognize collating symbol [[.].]] nor character class
_expression_ [[:alpha:]]
|
| |
| 33 |
sh_09 539 |
Within a bracket _expression_, an _expression_ within '[. .]' is treated
as a collating symbol when it is in the current collating sequence
and has characters associated with it.
|
N/A
To be fixed
|
Bash: does not recognize collating symbol [[.x.]-z].
|
| |
| 34 |
sh_09 543 |
Within a bracket _expression_, when a collating element is not a member
of a primary equivalent class and enclosed by '[= =]', then the
_expression_ matches the collating symbol.
|
N/A
To be fixed
|
Bash: does not recognize equivalence class _expression_ [[=x=]].
|
| |
| 35 |
sh_09 544 |
Within a bracket _expression_, one of the following character class
names within '[: :]' matches any collating element within the
character class: alnum, cntrl, lower, space, alpha, digit, print,
upper, blank, graph, punct, xdigit.
|
N/A
To be fixed
|
Bash: does not recognize character class _expression_ [[:xxx:]].
|
| |
| 36 |
sh_09 548 |
Within a bracket _expression_, the hyphen character is treated as
itself when one of the following occurs:
(1) it is first in the list
(2) it is first in the list after an initial exclamation mark (!)
(3) it is last in the list
(4) it is used as the ending point of a range _expression_
(5) it is used as a collating symbol
|
N/A
To be fixed
|
Bash: fails because it does not recognize collating symbol [[.-.]].
|
| |
| 37 |
sh_10 597 |
When a shell application is not executing a 'for', 'while' or 'until'
loop, then a call to 'break' has no effect. Execution continues with
the next command.
|
N/A
To be fixed
|
Bash: does not recognize 'break' outside of a 'for', 'while' , or
'until' loop.
|
| |
| 38 |
sh_10 600 |
Exit status of the break command is 0 upon successful completion.
|
N/A
To be fixed
|
Bash: does not recognize 'break' outside of a 'for', 'while' , or
'until' loop.
|
| |
| 39 |
sh_10 601 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 40 |
sh_10 603 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 41 |
sh_10 607 |
Exit status of the 'continue' is 0 upon successful completion.
|
N/A
To be fixed
|
Bash: does not recognize 'continue' outside of a 'for', 'while' , or
'until' loop.
|
| |
| 42 |
sh_10 608 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 43 |
sh_10 611 |
When $PATH is used to locate a file for the dot utility, then the file's
readable bit has to be set, executable bit is not important.
|
N/A
Intentional Exception
|
Bash: once bash finds a file with matching name; it looks at this file even if
this file is a non-readable and writes error message without searching
further down the path to find a readable file.
|
| |
| 44 |
sh_10 612 |
When no readable filename that matches 'file' is found using the
search path specified by PATH, then a non-interactive shell aborts.
|
N/A
To be fixed
|
Bash: does not abort non-interactive shell when no readable filename that
matches a given 'file' is found.
|
| |
| 45 |
sh_10 615 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command
|
| |
| 46 |
sh_10 620 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 47 |
sh_10 630 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 48 |
sh_10 642 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 49 |
sh_10 648 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 50 |
sh_10 652 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 51 |
sh_11 654 |
When 'set' is called with no options or arguments, then the format
of the output of the 'value' string is such that it is suitable for
re-input to the shell.
|
N/A
To be fixed
|
Bash: does not recognize the variable assignment contain a
blank (var="xxx yyy"). Bash takes yyy as the name of a command;
therefore, it writes a command (yyy) not found error message.
|
| |
| 52 |
sh_11 705 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 53 |
sh_12 722 |
If the implementation supports numeric signal numbers, then the
following mapping of signals to names is supported:
1 = SIGHUP 2 = SIGINT 3 = SIGQUIT 6 = SIGABRT
9 = SIGKILL 14 = SIGALRM 15 = SIGTERM
|
N/A
To be fixed
|
Bash: does not recognize ABRT or SIGABRT as valid signal name.
|
| |
| 54 |
sh_12 726 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |
| 55 |
sh_12 733 |
A variable assignment specified with a special built-in command
shall remain in effect after the built-in completes.
|
N/A
To be fixed
|
Bash: does not retain variable assignment specified with a special
built-in command.
|
| |