llvm-project/llvm/test/Other/close-stderr.ll

; RUN: sh -c "\
; RUN:        opt --reject-this-option 2>&-; echo \$?; \
; RUN:        opt -o /dev/null /dev/null 2>&-; echo \$?; \
; RUN:       " | FileCheck %s
; CHECK: {{^1$}}
; CHECK: {{^0$}}
; XFAIL: vg_leak

; Test that the error handling when writing to stderr fails exits the
; program cleanly rather than aborting.
Add a testcase to verify that commands don't crash when they hit errors on stderr. llvm-svn: 111440 2010-08-19 06:35:56 +08:00			`; RUN: sh -c "\`
Try to escape the '$'s in these so they reach the underlying 'sh' invocation. I have no idea how lit did the right thing here, but other test runners don't. llvm-svn: 111805 2010-08-23 16:54:19 +08:00			`; RUN: opt --reject-this-option 2>&-; echo \$?; \`
			`; RUN: opt -o /dev/null /dev/null 2>&-; echo \$?; \`
Add a testcase to verify that commands don't crash when they hit errors on stderr. llvm-svn: 111440 2010-08-19 06:35:56 +08:00			`; RUN: " \| FileCheck %s`
			`; CHECK: {{^1$}}`
			`; CHECK: {{^0$}}`
XFAIL test under valgrind. It is not really our problem if sh is leaking. llvm-svn: 113550 2010-09-10 06:02:13 +08:00			`; XFAIL: vg_leak`
Add a testcase to verify that commands don't crash when they hit errors on stderr. llvm-svn: 111440 2010-08-19 06:35:56 +08:00
			`; Test that the error handling when writing to stderr fails exits the`
			`; program cleanly rather than aborting.`