| Age | Commit message (Collapse) | Author |
|---|
|
patches, and i already had this sitting on my laptop at that time.. i used
that as a chance to note that we had all done the same work, more or less
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bug found by fgsch@openbsd.org. Patch mailed to pdksh maintainer.
|
|
|
|
some that we had already fixed locally.
o typeset -f FUNC doesn't print follows command (and expression) substitutions.
o when re-allocating memory, too much may be copied from old memory.
o set -o printed some options sans names.
o emacs mode: <esc>. in very fist command causes core dump.
o pdksh dumps core after a cd command.
o typeset -i reports on array elements that have no value
(at&t ksh reports on array base name - no index).
o ulimit -ctn unlimittttted kills shell (resource exceeded).
o ". /dev/null" says access denied.
o flag field in aliases incorrectly changed (all flags set instead of
clearing ISSET) in exec.c(flushcom).
o ${#array[*]} prints largest index instead of number of (set) elements
in an array (ksh88 does the former).
o sys_siglist[] doesn't always have NSIG non-null entries...
|
|
|
|
1) pkksh in sh mode closed fd's other than [012] on exec'ing a command.
this is a ksh'ism and POSIX sates that open files are part of the
environment to be passed to the new process.
2) pdksh in sh mode interpets (( as meaning the start of arithmetic
"quoting", which is incompatible with it's usage as a nested
sub-shell invocation. The $(( form for arithmetic substitution
is stil valid, however.
PR user/59 millert@openbsd.org (Todd C. Miller)
3) pdksh sh.1 manpage isn't explicit about the range of input text
that is subject to field splitting after a substitution.
PR user/236 Mathieu.Herrb@mipnet.fr (Mathiew Herrb)
|
|
|
|
|
|
|
|
|
|
|
