ANTLER Debug Environment

[larryk85]

This issue encapsulates over all of the tasks that are required to complete the ANTLER Debug Environment

By building upon our native test framework we have in CDT, we will create a new way to debug smart contracts in a few ways. As we move into the future and move to technologies like NatiVM, then this type of system will be even better fitting.

• Compile smart contracts as a 'shared object' to be loaded by the 'runner' (extending the framework that exists with the native compilation system) Debug Environment (antler-run) Compile Smart contracts as shared object #78
• Build the runner (functionality and API described in the ANTLER Project Design document). Debug Environment (antler-run) Creation of the Runner #79
• Build the leap plugin to expose host functions as an API endpoint for the runner to utilize and to 'pause' and direct control flow for a designated action on an account.
• Add LLDB as a build dependency of CDT to be used by end-users to debug their code. Debug Enviroment (antler-run) Add lldb as part of CDT build #80
• Add LLDB python module for smart contract dev usage. Debug Enviroment (antler-run) Add python module for dev usage #81
• Extend DUNE to use this new functionality.

[ericpassmore]

deprecating Antler closing issues as won't fix