File: t0652a.sh

package info (click to toggle)
libexplain 1.4.D001-16
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 42,228 kB
  • sloc: ansic: 156,043; makefile: 47,892; sh: 16,304; yacc: 1,898; awk: 245
file content (71 lines) | stat: -rw-r--r-- 2,239 bytes parent folder | download | duplicates (4) 
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
 
#!/bin/sh
#
# libexplain - a library of system-call-specific strerror replacements
# Copyright (C) 2011 Peter Miller
# Written by Peter Miller <pmiller@opensource.org.au>
#
# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by the Free
# Software Foundation; either version 3 of the License, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for
# more details.
#
# You should have received a copy of the GNU General Public License along with
# this program. If not, see <http://www.gnu.org/licenses/>.
#

TEST_SUBJECT='fputs("yuck", stdin);'
. test_prelude

# writing on stdin will usually barf, as this test case expectes,
# even if the underlying file descriptor was r/w before calling dup(2).
fmt > test.ok.1 << 'fubar'
fputs(s = "yuck", fp = stdin) failed, Bad file descriptor (EBADF)
because the fp argument does not refer to an object that is open for
writing; this is more likely to be a software error (a bug) than it is to
be a user error
fubar
test $? -eq 0 || no_result

# There is an alternative result, depending on the testing enviroment,
# because stdin may actually be closed.
fmt > test.ok.2 << 'fubar'
fputs(s = "yuck", fp = stdin) failed, Bad file descriptor (EBADF) because
the fildes argument does not refer to an object that is open for writing
(O_RDONLY | O_LARGEFILE)
fubar
test $? -eq 0 || no_result

test_fputs yuck stdin > test.out.4 2>&1
if test $? -ne 1
then
    set +x
    echo "it was supposed to fail" 1>&2
    cat test.out.4
    fail
fi

fmt -w 800  test.out.4 > test.out.3
test $? -eq 0 || no_result
sed 's/stdin "[^"]*")/stdin)/' test.out.3 > test.out.2
test $? -eq 0 || no_result
fmt test.out.2 > test.out
test $? -eq 0 || no_result

diff test.ok.2 test.out > /dev/null 2>&1 && pass

diff test.ok.1 test.out
test $? -eq 0 || fail

#
# Only definite negatives are possible.
# The functionality exercised by this test appears to work,
# no other guarantees are made.
#
pass

# vim: set ts=8 sw=4 et :