/
xtrace.test.sh
274 lines (248 loc) · 4.11 KB
/
xtrace.test.sh
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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
#
# xtrace test. Test PS4 and line numbers, etc.
#### set -o verbose prints unevaluated code
set -o verbose
x=foo
y=bar
echo $x
echo $(echo $y)
## STDOUT:
foo
bar
## STDERR:
x=foo
y=bar
echo $x
echo $(echo $y)
## OK bash STDERR:
x=foo
y=bar
echo $x
echo $(echo $y)
## END
#### xtrace with unprintable chars
case $SH in (dash) exit ;; esac
s=$'a\x03b\004c\x00d'
set -o xtrace
echo "$s"
## stdout-repr: 'a\x03b\x04c\x00d\n'
## STDERR:
+ echo $'a\x03b\x04c\x00d'
## END
## OK bash stdout-repr: 'a\x03b\x04c\n'
## OK bash stderr-repr: "+ echo $'a\\003b\\004c'\n"
# nonsensical output?
## BUG mksh stdout-repr: 'a;\x04c\r\n'
## BUG mksh stderr-repr: "+ echo $'a;\\004c\\r'\n"
## N-I dash stdout-json: ""
## N-I dash stderr-json: ""
#### xtrace with unicode chars
case $SH in (dash) exit ;; esac
mu1='[μ]'
mu2=$'[\u03bc]'
set -o xtrace
echo "$mu1" "$mu2"
## STDOUT:
[μ] [μ]
## END
## STDERR:
+ echo '[μ]' '[μ]'
## END
## N-I dash stdout-json: ""
## N-I dash stderr-json: ""
#### xtrace with tabs
case $SH in (dash) exit ;; esac
set -o xtrace
echo $'[\t]'
## stdout-json: "[\t]\n"
## STDERR:
+ echo $'[\t]'
## END
# this is a bug because it's hard to see
## BUG bash stderr-json: "+ echo '[\t]'\n"
## N-I dash stdout-json: ""
## N-I dash stderr-json: ""
#### xtrace with whitespace, quotes, and backslash
set -o xtrace
echo '1 2' \' \" \\
## STDOUT:
1 2 ' " \
## END
# Oil is different bceause backslashes require $'\\' and not '\', but that's OK
## STDERR:
+ echo '1 2' $'\'' '"' $'\\'
## END
## OK bash/mksh STDERR:
+ echo '1 2' \' '"' '\'
## END
## BUG dash STDERR:
+ echo 1 2 ' " \
## END
#### xtrace with newlines
# bash and dash trace this badly. They print literal newlines, which I don't
# want.
set -x
echo $'[\n]'
## STDOUT:
[
]
## STDERR:
+ echo $'[\n]'
## END
# bash has ugly output that spans lines
## OK bash STDERR:
+ echo '[
]'
## END
## N-I dash stdout-json: "$[\n]\n"
## N-I dash stderr-json: "+ echo $[\\n]\n"
#### xtrace written before command executes
set -x
echo one >&2
echo two >&2
## stdout-json: ""
## STDERR:
+ echo one
one
+ echo two
two
## OK mksh STDERR:
# mksh traces redirects!
+ >&2
+ echo one
one
+ >&2
+ echo two
two
## END
#### PS4 is scoped
set -x
echo one
f() {
local PS4='- '
echo func;
}
f
echo two
## STDERR:
+ echo one
+ f
+ local 'PS4=- '
- echo func
+ echo two
## END
## OK osh STDERR:
+ echo one
+ f
+ local PS4='- '
- echo func
+ echo two
## END
## OK dash STDERR:
# dash loses information about spaces! There is a trailing space, but you
# can't see it.
+ echo one
+ f
+ local PS4=-
- echo func
+ echo two
## END
## OK mksh STDERR:
# local gets turned into typeset
+ echo one
+ f
+ typeset 'PS4=- '
- echo func
+ echo two
## END
#### xtrace with variables in PS4
PS4='+$x:'
set -o xtrace
x=1
echo one
x=2
echo two
## STDOUT:
one
two
## END
## STDERR:
+:x=1
+1:echo one
+1:x=2
+2:echo two
## END
## OK mksh STDERR:
# mksh has trailing spaces
+:x=1
+1:echo one
+1:x=2
+2:echo two
## END
## OK osh/dash STDERR:
# the PS4 string is evaluated AFTER the variable is set. That's OK
+1:x=1
+1:echo one
+2:x=2
+2:echo two
## END
#### PS4 with unterminated ${
# osh shows inline error; maybe fail like dash/mksh?
x=1
PS4='+${x'
set -o xtrace
echo one
echo status=$?
## STDOUT:
one
status=0
## END
# mksh and dash both fail. bash prints errors to stderr.
## OK dash stdout-json: ""
## OK dash status: 2
## OK mksh stdout-json: ""
## OK mksh status: 1
#### PS4 with unterminated $(
# osh shows inline error; maybe fail like dash/mksh?
x=1
PS4='+$(x'
set -o xtrace
echo one
echo status=$?
## STDOUT:
one
status=0
## END
# mksh and dash both fail. bash prints errors to stderr.
## OK dash stdout-json: ""
## OK dash status: 2
## OK mksh stdout-json: ""
## OK mksh status: 1
#### PS4 with runtime error
# osh shows inline error; maybe fail like dash/mksh?
x=1
PS4='+oops $(( 1 / 0 )) \$'
set -o xtrace
echo one
echo status=$?
## STDOUT:
one
status=0
## END
# mksh and dash both fail. bash prints errors to stderr.
## OK dash stdout-json: ""
## OK dash status: 2
## OK mksh stdout-json: ""
## OK mksh status: 1
#### $? in PS1
PS4='[last=$?] '
set -x
false
echo ok
## STDOUT:
ok
## END
## STDERR:
[last=0] false
[last=1] echo ok
## END