blob: e3d5c749bdd9af407f8a609adccec59f7b012ad4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
#!/bin/sh
# basic tests for printf
prog=`pwd`/../../src/printf
if test "$VERBOSE" = yes; then
set -x
$prog --version
fi
pwd=`pwd`
t0=`echo "$0"|sed 's,.*/,,'`.tmp; tmp=$t0/$$
trap 'status=$?; cd $pwd; chmod -R u+rwx $t0; rm -rf $t0 && exit $status' 0
trap '(exit $?); exit $?' 1 2 13 15
framework_failure=0
mkdir -p $tmp || framework_failure=1
cd $tmp || framework_failure=1
if test $framework_failure = 1; then
echo "$0: failure in testing framework" 1>&2
(exit 1); exit 1
fi
fail=0
# This would fail (by printing the `--') for printf in sh-utils
# and in coreutils 4.5.1.
$prog -- 'foo\n' > out || fail=1
cat <<\EOF > exp
foo
EOF
cmp out exp || fail=1
test $fail = 1 && diff out exp 2> /dev/null
rm -f out exp
# Until coreutils-4.5.10, this would elicit a segfault.
$prog '1 %*sy\n' -3 x > out || fail=1
# Until coreutils-4.5.12, these would fail.
POSIXLY_CORRECT=1 \
$prog '2 \x' >> out || fail=1; echo >> out
$prog '3 \x40\n' >> out || fail=1
POSIXLY_CORRECT=1 \
$prog '4 \x40\n' >> out || fail=1
$prog '5 % +d\n' 234 >> out || fail=1
# This should print "6 !\n", but don't rely on `!' being the
# one-byte representation of octal 041. With printf prior to
# coreutils-5.0.1, it would print six bytes: "6 \41\n".
$prog '6 \41\n' | tr '\41' '!' >> out
# Note that as of coreutils-5.0.1, printf with a format of '\0002x'
# prints a NUL byte followed by the digit `2' and an `x'.
# By contrast bash's printf outputs the same thing as $(printf '\2x') does.
$prog '7 \2y \02y \002y \0002y\n' |tr '\0\2' '*=' >> out
$prog '8 %b %b %b %b\n' '\1y' '\01y' '\001y' '\0001y'|tr '\1' = >> out
cat <<\EOF > exp
1 x y
2 \x
3 @
4 \x40
5 +234
6 !
7 =y =y =y *2y
8 =y =y =y =y
EOF
cmp out exp || fail=1
test $fail = 1 && diff -au out exp 2> /dev/null
(exit $fail); exit $fail
|
