summaryrefslogtreecommitdiffstats
path: root/lldb/source/Host/common/DynamicLibrary.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Update LLDB to use LLVM's DynamicLibrary.Zachary Turner2014-08-271-33/+0
| | | | | | | | | LLDB had implemented its own DynamicLibrary class for plugin support. LLVM has an equivalent mechanism, so this patch deletes the duplicated code in LLDB and updates LLDB to reference the mechanism provided by LLVM. llvm-svn: 216606
* <rdar://problem/13209140>Enrico Granata2013-04-241-0/+6
| | | | | | “plugin load” tries to be more helpful when it fails to load a plugin llvm-svn: 180218
* Implementing plugins that provide commands.Enrico Granata2012-09-281-0/+27
This checkin adds the capability for LLDB to load plugins from external dylibs that can provide new commands It exports an SBCommand class from the public API layer, and a new SBCommandPluginInterface There is a minimal load-only plugin manager built into the debugger, which can be accessed via Debugger::LoadPlugin. Plugins are loaded from two locations at debugger startup (LLDB.framework/Resources/PlugIns and ~/Library/Application Support/LLDB/PlugIns) and more can be (re)loaded via the "plugin load" command For an example of how to make a plugin, refer to the fooplugin.cpp file in examples/plugins/commands Caveats: Currently, the new API objects and features are not exposed via Python. The new commands can only be "parsed" (i.e. not raw) and get their command line via a char** parameter (we do not expose our internal Args object) There is no unloading feature, which can potentially lead to leaks if you overwrite the commands by reloading the same or different plugins There is no API exposed for option parsing, which means you may need to use getopt or roll-your-own llvm-svn: 164865
OpenPOWER on IntegriCloud