Xcode doesn't pass these environment variables to lldb when it runs it, nor does it preprocess the .lldbinit files to insert these variables. We don't pass them to lldb as there's too much chance one of them really wouldn't be appropriate for lldb and cause hard to diagnose problems. And since .lldbinit files can contain arbitrary user expressions, preprocessing can also cause problems. Instead, the suggested way to do this is to make a target specific lldbinit file - as you have done - and in that file bring in all the .py files you need using command script import --relative-to-command-file ./my_python_files/my_python_file.py That allows you to give the paths to all your python files relative to the target-specific .lldbinit file without having to know where any of them actually are. Note, the same option exists for sourcing other files of lldb commands using command source.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: