Walter Erquinigo 1141ba677e [lldb-vscode] Follow up of D99989 - store some strings more safely ... As a follow up of https://reviews.llvm.org/D99989#inline-953343, I'm now storing std::string instead of char *. I know it might never break as char *, but if it does, chasing that bug might be dauting. Besides, I'm also checking of the strings gotten through the SB API are null or not.		2021-04-29 18:37:44 -07:00
..
bindings	[lldb] [gdb-remote server] Introduce new stop reasons for fork and vfork	2021-04-24 11:08:33 +02:00
cmake	…
docs	[lldb] [gdb-remote server] Introduce new stop reasons for fork and vfork	2021-04-24 11:08:33 +02:00
examples	[lldb] [gdb-remote server] Introduce new stop reasons for fork and vfork	2021-04-24 11:08:33 +02:00
include/lldb	[lldb] Correct format enum comment (NFC)	2021-04-28 12:17:03 +01:00
packages/Python	[lldb][AArch64] Don't check for VmFlags in smaps files	2021-04-29 09:30:14 +01:00
resources	…
scripts	…
source	[lldb] Make the NSSet formatter faster and less prone to infinite recursion	2021-04-29 19:13:43 +02:00
test	[lldb][AArch64] Don't check for VmFlags in smaps files	2021-04-29 09:30:14 +01:00
third_party/Python/module	…
tools	[lldb-vscode] Follow up of D99989 - store some strings more safely	2021-04-29 18:37:44 -07:00
unittests	[lldb] [llgs] Support owning and detaching extra processes	2021-04-24 11:08:33 +02:00
utils	…
.clang-format	…
.clang-tidy	…
.gitignore	…
CMakeLists.txt	…
CODE_OWNERS.txt	…
LICENSE.TXT	…
use_lldb_suite_root.py	…