aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorHector Diaz <hdiaz@fb.com>2020-03-19 14:08:40 -0700
committerWalter Erquinigo <waltermelon@fb.com>2020-03-20 18:51:25 -0700
commit4ec6ebabfc3ec03d3ad4d3bdf05a7292d01391b3 (patch)
treeae42f55cdb18f153707728746267b7b073df7d28 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parenta8c22ba4162976894b34b75fd12aced379e0569b (diff)
downloadllvm-4ec6ebabfc3ec03d3ad4d3bdf05a7292d01391b3.zip
llvm-4ec6ebabfc3ec03d3ad4d3bdf05a7292d01391b3.tar.gz
llvm-4ec6ebabfc3ec03d3ad4d3bdf05a7292d01391b3.tar.bz2
[lldb-vscode] Add inheritEnvironment option
Summary: If no custom launching is used, lldb-vscode launches a program with an empty environment by default. In some scenarios, the user might want to simply use the same environment as the IDE to have a set of working environment variables (e.g. PATH wouldn't be empty). In fact, most DAPs in VSCode have this behavior by default. In other cases the user definitely needs to set their custom environment, which is already supported. To make the first case easier for the user (e.g. not having to copy the PATH to the launch.json every time they want to debug simple programs that rely on PATH), a new option is now offered. inheritEnvironment will launch the program copying its own environment, and it's just a boolean flag. {F11347695} Reviewers: clayborg, aadsm, diazhector98, kusmour Subscribers: labath, JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D74636
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions