From 5dd4916f63f9820244d9fdd8d4bdd0f884f0e766 Mon Sep 17 00:00:00 2001 From: Jason Molenda Date: Wed, 6 Nov 2013 00:04:44 +0000 Subject: Add a new GetThreadOriginExtendedBacktrace method to the SystemRuntime and SBThread classes. llvm-svn: 194111 --- lldb/scripts/Python/interface/SBThread.i | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'lldb/scripts/Python/interface') diff --git a/lldb/scripts/Python/interface/SBThread.i b/lldb/scripts/Python/interface/SBThread.i index 4f678b6353c..3337c8d7848 100644 --- a/lldb/scripts/Python/interface/SBThread.i +++ b/lldb/scripts/Python/interface/SBThread.i @@ -240,6 +240,19 @@ public: bool operator != (const lldb::SBThread &rhs) const; + %feature("autodoc"," + Given an argument of str to specify the type of thread-origin extended + backtrace to retrieve, query whether the origin of this thread is + available. An SBThread is retured; SBThread.IsValid will return true + if an extended backtrace was available. The returned SBThread is not + a part of the SBProcess' thread list and it cannot be manipulated like + normal threads -- you cannot step or resume it, for instance -- it is + intended to used primarily for generating a backtrace. You may request + the returned thread's own thread origin in turn. + ") GetThreadOriginExtendedBacktrace; + lldb::SBThread + GetThreadOriginExtendedBacktrace (const char *type); + %pythoncode %{ class frames_access(object): '''A helper object that will lazily hand out frames for a thread when supplied an index.''' -- cgit v1.2.3