4 Commits

Author	SHA1	Message	Date
Nathan Lanza	a0d52cbdc9	Add a check whether or not a str is utf8 prior to emplacing ... Summary: Highlighing junk data on VSCode can send a query for evaluate which fails. In particular cases on Windows, this the error message can end up as a c-string of [-35,-35,-35,-35,...]. Attempting to emplace this as the error message causes an assert failure. Prior to emplacing the error message, confirm that it is valid UTF8 to eliminate errors such as mentione above. Reviewers: xiaobai, clayborg Reviewed By: clayborg Differential Revision: https://reviews.llvm.org/D53008 llvm-svn: 346988	2018-11-15 19:49:57 +00:00
Bruce Mitchener	173946dca6	Fix typos. ... Reviewers: lldb-commits Subscribers: srhines, ki.stfu Differential Revision: https://reviews.llvm.org/D52884 llvm-svn: 343825	2018-10-04 22:33:39 +00:00
Reid Kleckner	8b5e6991d2	Fix lldb-vscode build on Windows ... Include PosixAPI.h to get a PATH_MAX definition and replace CreateEvent with CreateEventObject to avoid conflicts with the windows.h definition of CreateEvent to CreateEventW. llvm-svn: 339920	2018-08-16 18:24:59 +00:00
Greg Clayton	2f5cf8511a	Add a new tool named "lldb-vscode" that implements the Visual Studio Code Debug Adaptor Protocol ... This patch adds a new lldb-vscode tool that speaks the Microsoft Visual Studio Code debug adaptor protocol. It has full unit tests that test all packets. This tool can be easily packaged up into a native extension and used with Visual Studio Code, and it can also be used by Nuclide Differential Revision: https://reviews.llvm.org/D50365 llvm-svn: 339911	2018-08-16 17:59:38 +00:00