llvm-project/clang-tools-extra/clangd/test/too_large.test

# RUN: not clangd -sync < %s 2>&1 | FileCheck -check-prefix=STDERR %s
# vim: fileformat=dos
# It is absolutely vital that this file has CRLF line endings.
#
Content-Length: 2147483648

# STDERR: Refusing to read message
[clangd] Rename -run-synchronously to -sync llvm-svn: 361798 2019-05-28 17:20:57 +08:00			`# RUN: not clangd -sync < %s 2>&1 \| FileCheck -check-prefix=STDERR %s`
[clangd] Don't crash on extremely large JSON messages. Found by clangd-fuzzer. llvm-svn: 316774 2017-10-28 01:06:41 +08:00			`# vim: fileformat=dos`
			`# It is absolutely vital that this file has CRLF line endings.`
			`#`
			`Content-Length: 2147483648`

[clangd] Rewrite JSON dispatcher loop using C IO (FILE*) instead of std::istream. Summary: The EINTR loop around getline was added to fix an issue with mac gdb, but seems to loop infinitely in rare cases on linux where the parent editor exits (most reports with VSCode). I can't work out how to fix this in a portable way with std::istream, but the C APIs have clearer contracts and LLVM has a RetryAfterSignal function for use with them which seems battle-tested. While here, clean up some inconsistency around \n in log messages (now add it only after JSON payloads), and reduce the scope of the long-message handling which was only really added to fight fuzzers. Reviewers: malaperle, ilya-biryukov Subscribers: klimek, ioeric, jkorous, cfe-commits Differential Revision: https://reviews.llvm.org/D47643 llvm-svn: 333993 2018-06-05 17:34:46 +08:00			`# STDERR: Refusing to read message`