Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [lldb] Handle EOF from `lldb-vscode` | Jan Kratochvil | 2019-07-16 | 1 | -0/+5 |
| | | | | | | | | | | | | | | | | | | | | | | | Sometimes (when running lldb-vscode under strace) I get: read(0, "", 16) = 0 read(0, "", 16) = 0 read(0, "", 16) = 0 ... With this patch testcases finish properly even with strace: read(0, "", 16) = 0 futex(0x1346508, FUTEX_WAKE_PRIVATE, 2147483647) = 0 stat("", 0x7ffe8f2634c8) = -1 ENOENT (No such file or directory) --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=9124, si_uid=1001, si_status=SIGINT, si_utime=1, si_stime=0} --- close(4) = 0 exit_group(0) = ? +++ exited with 0 +++ Differential Revision: https://reviews.llvm.org/D64698 llvm-svn: 366187 | ||||
* | [lldb-vscode] Fix warning | Jonas Devlieghere | 2019-03-08 | 1 | -2/+2 |
| | | | | | | | | I changed the variable to an unsigned to get rid of a signed and unsigned compare without realizing the value could be negative. This fixes the assert instead. llvm-svn: 355708 | ||||
* | Make bytes_read an unsigned | Jonas Devlieghere | 2019-03-07 | 1 | -1/+1 |
| | | | | llvm-svn: 355651 | ||||
* | [lldb-vscode] Support running in server mode on Windows. | Zachary Turner | 2019-03-07 | 1 | -0/+153 |
Windows can't use standard i/o system calls such as read and write to work with sockets, it instead needs to use the specific send and recv calls. This complicates matters for the debug adapter, since it needs to be able to work in both server mode where it communicates over a socket, as well as non-server mode where it communicates via stdin and stdout. To abstract this out, I've introduced a class IOStream which hides all these details and exposes a read/write interface that does the right on each platform. Differential Revision: https://reviews.llvm.org/D59104 llvm-svn: 355637 |