summaryrefslogtreecommitdiff
path: root/gitweb
diff options
context:
space:
mode:
authorLibravatar Karsten Blees <karsten.blees@gmail.com>2014-06-14 00:09:06 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-06-16 10:56:19 -0700
commit51822653f58e6b9b6119f560ff864813fbde81ba (patch)
treea4d932b93c0b699202688b84866fea4c5e1acaa9 /gitweb
parentWin32: fix broken pipe detection (diff)
downloadtgif-51822653f58e6b9b6119f560ff864813fbde81ba.tar.xz
Win32: reliably detect console pipe handles
As of "Win32: Thread-safe windows console output", child processes may print to the console even if stdout has been redirected to a file. E.g.: git config tar.cat.command "cat" git archive -o test.cat HEAD Detecting whether stdout / stderr point to our console pipe is currently based on the assumption that OS HANDLE values are never reused. This is apparently not true if stdout / stderr is replaced via dup2() (as in builtin/archive.c:17). Instead of comparing handle values, check if the file descriptor isatty() backed by a pipe OS handle. This is only possible by swapping the handles in MSVCRT's internal data structures, as we do in winansi_init(). Reported-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Karsten Blees <blees@dcon.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'gitweb')
0 files changed, 0 insertions, 0 deletions