aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2013-10-14 21:39:38 +0000
committerEnrico Granata <egranata@apple.com>2013-10-14 21:39:38 +0000
commitc0f8ca0e74f85241aafa8291f207ceb7e5dfe22b (patch)
tree1edc04cc96c8f6737494f49c1b7d52d9a51e6ded /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent2453a3d95624f993f345c8f4a8513351e0c8da66 (diff)
downloadllvm-c0f8ca0e74f85241aafa8291f207ceb7e5dfe22b.zip
llvm-c0f8ca0e74f85241aafa8291f207ceb7e5dfe22b.tar.gz
llvm-c0f8ca0e74f85241aafa8291f207ceb7e5dfe22b.tar.bz2
Add the capability for LLDB to query an arbitrary Python module (passed in as a file path) for target-specific settings
This is implemented by means of a get_dynamic_setting(target, setting_name) function vended by the Python module, which can respond to arbitrary string names with dynamically constructed settings objects (most likely, some of those that PythonDataObjects supports) for LLDB to parse This needs to be hooked up to the debugger via some setting to allow users to specify which module will vend the information they want to supply llvm-svn: 192628
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions