[lldb-dev] RFC: full support for python files, and avoid using FILE* internally

[Lawrence D'Anna via lldb-dev]

> On Sep 24, 2019, at 10:04 AM, Ted Woodward <tedwood at quicinc.com> wrote:
> 
> A bit of a tangent, but I've been getting requests to debug Python and C++ together. Things like TensorFlow start in Python, then call into C++ libraries. Users want to be able to debug the Python code as Python (not debugging into Python itself), then step into the C++ libraries. They want to go up and down the stack, switching languages as needed. "What was my Python code doing when it called into the library. Now what is the library doing?"

Python does have a tool called faulthandler that can produce python stack traces when the interpreter experiences a segfault.  I wonder if there’s a way for LLDB invoke that to get python backtraces in the debugger?